Flutter vs React Native vs native: which should your business build?

What you are actually choosing between

Native means two apps: Swift for iOS, Kotlin for Android, two codebases to keep in step forever. React Native means one codebase in JavaScript or TypeScript that renders the platform's own components — the buttons are real iOS and Android buttons. Flutter means one codebase in Dart that draws its own components on a canvas, so the app looks exactly the same everywhere because Flutter is painting every pixel itself.

That last difference is the whole argument. React Native inherits each platform's look; Flutter overrides it. Neither is better in the abstract — it depends on whether you want your app to feel like an iPhone app on an iPhone, or to look like your brand on every device.

When Flutter is the right call

• The interface is the product — custom components, heavy animation, a design system you do not want the platform overriding.
• The app must look identical on both platforms, which matters for brand-led consumer apps and for training staff on one screen layout.
• You want the rendering to behave the same on a cheap Android device as on a new iPhone, which Flutter's own rendering engine makes more predictable.
• The team already writes Dart, or is starting fresh with no JavaScript codebase to share with.

When React Native is the right call

• You already have a web app in React or Next.js — types, validation, API clients and business logic can be shared rather than rewritten.
• You want the app to feel native on each platform, adopting iOS and Android conventions rather than one imposed look.
• Hiring matters: any competent React developer can work on it, which is a far larger pool than Dart.
• You need to ship fixes without waiting for store review, which over-the-air updates make routine.

When fully native still wins

1. Heavy camera or media work — custom capture pipelines, real-time filters, video editing.
2. Continuous background sensing — fitness tracking, navigation, anything reading sensors for hours.
3. Demanding real-time graphics — games, AR, 3D visualisation.
4. A critical vendor SDK with no maintained cross-platform bridge, which still happens with some banking, hardware and industrial suppliers.

The parts people forget to scope

• Offline behaviour. Field, warehouse and delivery teams work without signal. What is stored locally and how conflicts resolve on sync is a design decision, not a library choice — and it is the same decision in both frameworks.
• Push notifications. Cheap to add, expensive to get right: permissions, deep links into the correct screen, and not training users to ignore you.
• Updates. React Native can ship most fixes over the air; Flutter and native cannot to the same degree. For an app your own staff use daily, that difference is felt weekly.
• Store submission. Developer accounts, listings, screenshots, privacy declarations and the review cycle take real calendar time. Budget a week.

Cost and timeline

A first cross-platform release covering both stores starts around $1,499 in either framework, and typically takes a few weeks for a working slice that real users can hold, then extends in iterations. The same scope built natively twice lands closer to double, and the gap widens with every feature added afterwards.