React Native lets you build an iOS and an Android app from one JavaScript codebase. Native development means writing each app in its platform's own language: Swift for iOS and Kotlin for Android. Both produce real apps from the stores, and both are used by large, successful products.
We have made this decision on our own money. FAM, our family organiser, launched as a React Native app and was rebuilt in native Kotlin with Jetpack Compose in 2026. PivotBank and Ledger Drill were native from day one. This is what that taught us.
Where React Native is the right choice
- You need both stores quickly with a small team, and most screens are forms, lists, and content.
- Your team already writes React for the web and can share logic and people across both.
- The app is a companion to a web product rather than the main way people use it.
- You want to test demand on both platforms before investing in two native apps.
Where native wins
- Home screen widgets, background work, and deep system features are central to the product.
- Performance and smoothness are part of the experience, such as heavy lists, animation, or camera work.
- You want the newest platform features the day they ship, without waiting for a library to support them.
- The app is the product and will be maintained for years, so long-term stability matters more than speed to launch.
Why we rebuilt FAM natively
FAM's value grew around things that live on the phone itself: widgets on the home screen, reminders that fire reliably in the background, and quick voice input. Each of those was possible in React Native, but each needed native code and extra libraries, and every platform update risked breaking something. Moving to Kotlin and Jetpack Compose made those features first-class and made upgrades predictable.
The rebuild was not a verdict that React Native is bad. It was the right tool for getting FAM launched and learning what families actually used. Once we knew, native was the right tool for making those parts excellent.
Cost, honestly
React Native is usually cheaper for a first version on both platforms, because most of the code is shared. The gap narrows as an app grows more platform-specific features, because each one needs native work anyway. Native costs more up front for two platforms, but can cost less to maintain for an app that leans heavily on the phone's own capabilities.
How to decide for your app
- 01List the features that depend on the phone itself: widgets, background tasks, camera, Bluetooth, health data, or billing.
- 02Decide whether you need both stores at launch or can start with one.
- 03Consider who will maintain the app in two years, and which skills they have.
- 04If the list in step one is short and launch speed matters most, start with React Native. If it is long and central to the product, go native.
Whichever you choose, start with a prototype of the riskiest feature on a real device. It settles the question faster than any comparison chart.