Should a UK startup choose Flutter or React Native?

On the UK hiring market the gap is wide: 217 permanent UK vacancies mentioned React Native in the six months to 5 October 2026, against 24 that mentioned Flutter, and Flutter vacancies fell from 39 the year before. If somebody other than the original developer will have to maintain the app, React Native is materially easier to staff in Britain.

Is Flutter worse than React Native?

No. As engineering they are close enough that the choice rarely turns on capability, and Flutter has real advantages in rendering consistency. The difference that matters to a founder is the size of the pool of people who can pick the project up later, and in the UK that pool is roughly nine times larger for React Native.

What about native iOS and Android instead?

Native is the right answer when the app depends on platform features that cross-platform frameworks reach awkwardly, such as background Bluetooth, health data, or widgets and Live Activities. It costs more because it is two codebases. UK hiring is healthy for both: 276 vacancies mentioned Kotlin and 71 mentioned Swift in the same window.

Tech choice

Flutter or React Native, if you are building in the UK?

Last updated 7 October 2026

Every comparison of these two is a feature table written by somebody who builds in one of them. The feature tables are not wrong, they are just answering a question you do not have. Here is the one you do have, with the British numbers attached.

The question is not which is better. It is who maintains it.

You are commissioning an app. In eighteen months somebody who is not the person who built it will need to change it — because you hired in-house, because the agency moved on, because the freelancer took a full-time job. That is not a pessimistic scenario, it is the normal one.

So the question that actually decides this is: in two years, in Britain, how hard will it be to find someone who can pick this up? That is a measurable thing, and nobody writing these comparisons measures it.

Framework	UK permanent vacancies	Median salary	Year on year
React Native	217	£80,000	Rank fell 57 places; pay up 3.2%
Flutter	24	£75,000	Vacancies fell from 39; pay up 11.1%
Kotlin (native Android)	276	£70,000	Vacancies rose from 154
Swift (native iOS)	71	£75,000	Pay up 11.1%

ITJobsWatch, UK permanent vacancies, six months to 4–6 October 2026 depending on the skill. Salary samples: React Native 161 quotes, Flutter 14, Kotlin 196, Swift 46. The Flutter median rests on fourteen data points and should be read as an indication, not a benchmark — but the vacancy count, which is the number that matters here, is a full count rather than a sample.

Nine to one

That is the ratio that should drive the decision. React Native appears in roughly nine times as many British job adverts as Flutter. And the direction of travel is not kind to Flutter either: UK vacancies mentioning it fell from 39 to 24 over the year, and its rank among tracked skills dropped 167 places.

Two honest caveats on that. First, small numbers move around; 24 against 39 is a real decline but it is a decline in a small absolute figure. Second, vacancy counts measure employers advertising for a named skill, which under-counts freelancers and agencies — the people you are most likely to hire for an app project. The ratio is still the best public proxy available for how deep each pool is in Britain, and no feature table offers anything comparable.

Why Flutter pays more per head

Worth noticing that Flutter salaries rose 11.1% while React Native rose 3.2%. Scarcity does that. It is good news if you are a Flutter developer and bad news if you are hiring one: fewer candidates, each costing more, in a market where your fallback option is to rewrite.

When the answer is Flutter anyway

Hiring depth is the strongest single argument and it is not the only one. Pick Flutter when:

The person building it is a Flutter developer and will keep maintaining it. A team working in the thing they know beats a team working in the thing with better statistics. This covers most small projects honestly.
The design is unusual and must be pixel-identical on both platforms. Flutter draws its own widgets rather than wrapping the platform ones, which makes a heavily custom interface more predictable.
You are already in the Google ecosystem and the app is a companion to something built on Firebase that your team runs.

And when it is neither

Go native when the app leans on platform features that cross-platform frameworks reach only through bridging code somebody has to write anyway: background Bluetooth, health data, continuous background location, widgets and Live Activities, serious real-time media. At that point you are paying for native work inside a cross-platform project, which is the worst of both. The UK can staff both native stacks comfortably — 276 Kotlin vacancies and 71 Swift.

What I would tell you if you asked me on a call

If you have no existing team and no exotic hardware requirements, React Native, mostly because it keeps your options open and the decision is reversible by hiring rather than rewriting. If you already have a Flutter developer you trust, keep them; the hiring argument is about your fallback, not your first choice, and a good developer in the wrong framework beats an absent one in the right framework.

The decision that genuinely costs money is not this one. It is choosing cross-platform at all when the product needed native, and discovering it six months in.

Sources. ITJobsWatch React Native, Flutter, Kotlin and Swift, UK permanent vacancies, six-month windows ending 4–6 October 2026, retrieved 7 October 2026. Sample sizes are stated above because two of the four are small. The recommendation at the end is my opinion, not a finding.

Want this decided for your project?

Tell me what the app has to do and who will maintain it. You get a recommendation with the reasoning, and no attachment on my side to either answer.

Start here →