React Native, Flutter or native? A practical decision guide

“Which framework should we use?” is usually the first question in a mobile project, and it is rarely the most important one. All three options can produce excellent apps. The right choice depends on what the app does, who will maintain it and how it fits with the rest of your product.

Here is how we think it through with clients.

The short answer

For most business apps (marketplaces, booking, internal tools, content and commerce), a cross-platform framework is the sensible default. You get one codebase, one team and both app stores, and users will not notice the difference.

Go fully native when the app’s core experience depends on things cross-platform frameworks handle less gracefully: heavy real-time graphics, deep hardware integration, or experiences that must feel distinctly at home on one platform.

When cross-platform is the right call

Cross-platform shines when most of the app is screens, lists, forms and network calls, which describes most apps.

• Budget and speed. One codebase means fewer engineers and features shipping to both platforms at once.
• A web team already exists. React Native lets web engineers contribute, and shared TypeScript types reduce mistakes between app and API.
• Frequent updates. Over-the-air updates let you fix many issues without waiting for store review.

The trade-off is that you depend on the framework’s bridge to native features. Popular capabilities are well covered; unusual ones may need custom native modules, which is still far cheaper than building two apps.

When native earns its cost

Native Swift and Kotlin development costs more because you build twice, but sometimes that is exactly what the product needs.

• Graphics and real-time media. Camera pipelines, AR, audio processing and complex animations run closest to the metal natively.
• Deep platform features. Widgets, watch apps, health data, Bluetooth peripherals and background processing are first-class natively.
• Platform-defining experiences. If the app must feel like it was made by Apple or Google, native UI toolkits make that easiest.

A hybrid is also common: a cross-platform app with a few native modules for the parts that need them.

React Native vs Flutter

Both are mature and both are used in apps with millions of users. The differences that matter in practice:

Consideration	React Native	Flutter
Language	TypeScript / JavaScript	Dart
UI approach	Native platform components	Its own rendering engine
Fits well with	React and Next.js web teams	Teams starting fresh on mobile
Look and feel	Closest to each platform by default	Pixel-identical across platforms
Code sharing with web	Logic, types and sometimes UI	Limited

If your company already builds the web in React, React Native usually wins on hiring and code sharing. If you want a highly custom, brand-led interface that looks identical everywhere, Flutter is excellent.

The questions we ask before recommending

We put our recommendation in writing, and it comes from answers to questions like these:

1. Which three features would make or break the app, and how dependent are they on hardware or platform APIs?
2. Who will maintain the app in two years, and what languages does that team know?
3. How much code or logic should be shared with the website or other apps?
4. How often will you ship updates, and how important are fixes that skip store review?
5. What do the first year’s budget and timeline realistically allow?

What matters more than the framework

Teams spend weeks debating frameworks and hours on the things that actually decide whether an app succeeds:

• Offline behaviour. What happens on a train, in a basement, or with one bar of signal?
• Performance on cheap phones. Your users are not all on the latest flagship.
• Release engineering. Automated builds, staged roll-outs and crash reporting from the first beta.
• The backend. A fast, well-designed API improves the app more than any framework choice.

Get those right and any of the three options will serve you well. Get them wrong and no framework will save the app.