Proposals mention React Native, Flutter, native — which framework should we pick for our first app?

Technically speaking, the main difference lies in how they access hardware. React Native talks to native components over a bridge, while Flutter draws pixels directly using its own graphics engine. On ordering and invoice screens, that difference comes down to milliseconds; the end user will never notice. As long as you aren't hammering the hardware, both frameworks are more than enough.

We launched a similar wholesale app on React Native two years ago. Development ran us 30,000 dollars, and we spend around 4,000 dollars a year on hosting and maintenance. If we had gone native, we'd have needed two separate devs; ongoing costs would have blown our budget in year one.

The single codebase idea sounds amazing on paper, but OS updates can get frustrating at times. Whenever a new mobile OS version rolls out, you might end up waiting weeks for certain packages to get updated. Make sure to clearly define the terms for version compatibility support when signing with the agency.

the agency pitching native is probably used to dealing with huge corporate clients not worth that kind of money at all. honestly a restaurant owner cares about a smooth ui not whether the code is swift flutter will do the job just fine.

I'd suggest deciding based on these three points: 1) The agency's portfolio with similar B2B projects, 2) The complexity of third-party integrations like barcode scanning or maps, 3) Their hourly maintenance rates after launch.

Have you discussed how the app will communicate with your existing ERP or accounting system? More than the framework choice, whether your API endpoints are ready or not can hit your budget way harder. If your database isn't ready for mobile services yet, agencies might hit you with extra integration fees.

were in a similar spot.. then like if we start with cross-platform will we eventually be forced to rewrite everything in native if the app scales significantly? would that mean rebuilding entirely from scratch?

Download two apps built by the agency proposing Flutter and test out the ordering flow. If it runs smooth and their clients are happy, take the 28,000 dollar offer. Put that 27,000 dollar difference toward marketing and onboarding your customers instead.

I'm a small business, let me explain from my side. Payment schedules should be tied to project phases, not calendar dates.

This is my opinion, I'm not claiming it's absolute truth.

how did you solve this? most time waste accumulates in tasks waiting for approval.

just leaving this note, it might be useful.

You're right. Everything goes well for the first three months; problems arise in the fourth.

I'm also curious if anyone does it differently.

Let me summarize what's been said so far. Everyone rushing into mobile app development frameworks gets stuck at the same point.

If it's your first time, start small; scaling comes later. That's all, sorry if I went on too long.

I have a question. Processes without records never improve, because you don't know what to fix.

If code ownership isn't in the contract, you have no bargaining power when leaving. Of course, it varies if your situation is different.

I didn't know that.

Thanks, that was the answer I was looking for. Mistakes made on the mobile app development frameworks side are usually reversible but expensive.

Just leaving this note, it might be useful.

we got stuck at the same point for a while but when making decisions write down the worst-case scenario too, not just the best.

good luck with that.

i agree then processes without records never improve, because you dont know what to fix.

Let me speak from the other side; I'm on the supplier side. Solutions that work at a small scale collapse when you grow; I learned this late.