“Should we build native or cross-platform?” is one of the first questions on any mobile project — and the honest answer is: it depends on what the app needs to do. Here’s the pragmatic framework we use to decide, without the tribalism.
When cross-platform wins
For most apps — content, commerce, booking, dashboards, social — a single React Native or Expo codebase is the right call. You ship to iOS and Android at once, share business logic, and move faster with a smaller team. Modern React Native is genuinely native under the hood: real platform views, native navigation, and near-native performance for the vast majority of interactions.
- Tight budget or timeline, two platforms required.
- A product that’s mostly screens, lists, forms and networking.
- A team that already lives in TypeScript and React.
When fully native earns its cost
Some apps genuinely benefit from Swift and Kotlin. If the product’s core value is the platform — heavy graphics, real-time camera or AR, low-level Bluetooth, audio processing, or bleeding-edge OS features on day one — native gives you the control and performance headroom that abstractions can’t.
- Games and graphics-intensive experiences.
- Deep hardware or sensor integration.
- Apps where a 16ms frame budget is a hard requirement everywhere.
The decision in practice
We start from the features, not the framework. Map the handful of interactions that define the product, ask whether cross-platform can deliver them at the quality bar you need, and only reach for native where it clearly pays for itself. Often the answer is a hybrid: React Native for the app, with a native module for the one demanding feature.
Frameworks are a means, not a religion. Choose the one that ships the product your users deserve — and be ready to justify the choice with the feature list, not a preference.