Should we choose Flutter or React Native for a mobile app project? Does the agency's preference tie our hands?

React Native communicates with native OS components over a bridge, whereas Flutter paints pixels directly to the screen using its own graphics engine. On the older or low-spec Android tablets used by field reps, Flutter stutters noticeably less during UI scrolling and filling out forms.

When building our internal team, we posted openings for both. Two years ago, applicants who knew React outnumbered those who knew Flutter almost three to one. Lately, though, the ratio of Flutter developers among fresh graduates has climbed significantly. If you're looking for senior talent, finding alternatives is still easier on the React side.

Correction: I misremembered the figure, it was a bit lower.

Agencies usually praise whichever stack their idle developers happen to know best as the absolute best. An agency pushing Flutter often lacks React talent, while one pushing React probably has weak Flutter experience. Before getting hung up on the stack, download and test live reference apps that both agencies have previously shipped to the stores.

Ask the agencies these three questions before deciding: 1) Can it store orders locally and sync automatically when field reps lose their internet connection? 2) Will they use prebuilt packages for the barcode and camera scanning modules? 3) Will they hand over an architectural diagram and technical documentation upon completion?

no matter which one u pick if u don't own the repos u'll be tied to the agency anyway. add a clause in the contract for weekly code handovers the rest doesn't matter that much both stacks will get the job done just fine.

We had our first version built in Flutter by another agency. When we had a falling out with them, we pulled the code and started looking for an in-house developer. Within two weeks, we hired a really talented dev through a job posting who took over the project smoothly. We didn't face the lock-in we had feared.

Get input from whoever built your existing web infrastructure, too. If your web portal was developed using a modern front-end library, choosing React Native allows you to share common components and data models, which can slash your future maintenance costs significantly.

Were in a similar position. If we pick one of these two stacks we wont need to employ two separate developers for iOS and Android down the road, right? My understanding is that both platforms build from a single codebase is that correct?

I didn't know that. If acceptance criteria aren't written, when the work is done is open to debate.

If you post the result here, it will help others too.

I completely agree. Hasty decisions become decisions you have to fix six months later.

When making decisions, write down the worst-case scenario too not just the best. If I were you, I'd go this route.

We experienced almost the exact same thing last year. The real issue isn't the number, but what it's based on.

Three different views emerged they all complement each other. If acceptance criteria aren't written, when the work is done is open to debate.

Correct me if I'm wrong.

It's rare to find an explanation this clear. Any unwritten clause becomes a point of disagreement later, as both sides remember it differently.

If code ownership isn't in the contract, you have no bargaining power when leaving.

Noted, thanks... I mean start with a small trial; don't commit to everything at once.

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

i went through the same thing.

I'm writing this so you don't make the same mistake. Mistakes made on the Flutter or React Native side are usually reversible but expensive.

When making decisions, write down the worst-case scenario too, not just the best.

There's a common mistake people make when doing this. Every "we'll look at it later" in a meeting means unbilled work.

Correct me if I'm wrong.

looking at it as a process, the picture changes. honestly dont hesitate to ask; those who dont ask always pay more.

prven by experience.