If your app depends on one platform’s features, or you only need one platform at first, native development is usually the safer choice. If you need iPhone and Android with mostly shared screens and logic, a cross-platform framework can cut duplicated work. Between Flutter and React Native, the deciding factors are usually your team’s skills and the libraries your key features need.
The three options at a glance
| Native | Flutter | React Native | |
|---|---|---|---|
| Codebase | Separate apps: Swift for iOS, Kotlin for Android | One codebase in Dart | One codebase in JavaScript or TypeScript |
| User interface | Each platform’s own components | Flutter draws its own interface, so screens match on both platforms | Uses each platform’s own interface components |
| Often a good fit for | Apps built around device features, or one platform first | Custom, branded designs on iPhone and Android | Teams and products already using React on the web |
| Plan for | Building and maintaining features twice for two platforms | Native code for some platform-specific features | Checking that the libraries your features need are maintained |
When native development is the better choice
- You’re launching on one platform first. A cross-platform framework saves the most when you ship to both stores.
- Your core features depend on the device. Examples include Home Screen widgets, Apple Watch apps, augmented reality, advanced camera or audio processing, and Bluetooth hardware. Cross-platform apps can use these through plugins or native modules, but each one adds platform-specific code to maintain.
- You want new operating system features soon after release. Apple and Google publish new features for their own tools first.
Our iOS app development and Android app development pages describe how we approach native projects.
When Flutter fits
- You need iPhone and Android apps that share most of their screens and business logic.
- Your design is custom and should look the same on both platforms.
- You don’t have an existing JavaScript codebase or team to build on.
Plan for native code where a feature needs it, and check the packages your app will depend on. See Flutter app development.
When React Native fits
- Your team or product already uses React and TypeScript on the web.
- You want each platform’s own interface controls.
- You want to share developer skills, and some non-interface code, with a web app.
Before choosing it, check that the libraries for your key features are actively maintained, and plan time for React Native version upgrades. See React Native development.
What about cost and timeline?
One cross-platform codebase can reduce duplicated work when both platforms share most of their screens. The saving shrinks if many features need separate native code for each platform. Instead of relying on a general rule, ask for an estimate of each option based on your own feature list.
The backend is usually the same whichever option you choose. If your app needs accounts, bookings or data shared between users, include backend development in your estimate.
Questions to answer before you decide
- Which platforms must be ready at launch, and which can follow later?
- Which device features are essential to the first release?
- Who will maintain the app after launch, and which languages do they know?
- Is there an existing app, web app or API you need to build on?
- How custom is the design, and should it look the same on both platforms?
Record your answers in a mobile app project brief. That gives a development team enough detail to recommend an approach and estimate it.