The tech decision for a mobile app takes an hour of discussion and affects the project for years. Most content online argues it dogmatically: one camp says native always wins, another says Flutter already won. The truth is it depends on your app type and who will maintain it.
The core difference in one sentence
Native means two separate apps: Kotlin for Android, Swift for iOS. Cross-platform (Flutter or React Native) means one codebase compiled for both.
The direct consequence: native costs roughly 1.5–2x cross-platform, because you build and maintain two codebases.
When to pick cross-platform (most cases)
If your app is screens, data and an API — a store, a services app, booking, a dashboard, delivery — Flutter gives you nearly the same result at half the cost and half the maintenance.
The real advantage isn't the upfront price, it's maintenance. Every change is made once instead of twice, every bug fixed once. Over three years that gap exceeds the original build cost.
Flutter is the more mature choice: performance close to native because it draws its own UI, and identical appearance across platforms. React Native wins if your team already writes JavaScript or you have a React web app and want to share business logic.
When native earns the extra money
Some cases make cross-platform a constant fight:
- Deep hardware use: real-time camera processing, video processing, Bluetooth LE, AR.
- Games or heavy graphics — those have their own engines like Unity anyway.
- Performance-critical apps where every millisecond counts.
- Needing an OS feature released yesterday, with no time to wait for a wrapper package.
Also, if your audience is on one platform only — many internal company apps are Android-only — single-platform native makes perfect sense.
The option we often recommend: start with web
Before paying for an app at all, ask: does the user need to open this daily? If not, a responsive website (or PWA) reaches the same audience at a third of the cost, with no app-store review and no download required.
An app earns its place when you need push notifications, offline operation, hardware access, or when usage is frequent enough that an icon on the home screen has real value.
What nobody warns you about: post-launch cost
An app doesn't end at launch. Google and Apple update their platforms yearly and stores impose new requirements. Go long enough without an update and your app can be removed.
Budget 15–20% of the build cost annually for maintenance. That's not optional — it's part of owning an app.
Bottom line
For most business apps, Flutter is the rational choice. Native when you have a specific technical reason you can name. And if you're still testing the idea — start with a responsive site and wait until real users ask for the app.