Write to usDiscuss a project
All articles

Native or cross-platform: how to choose

Four questions that decide whether an app is written once or twice.

A native app is written separately for iOS (Swift) and Android (Kotlin). A cross-platform app shares most of its code between both, using Flutter or React Native. Neither is better in general. The product decides.

Four questions

  1. How much of the app is ordinary screens? Lists, forms, profiles and checkout look and behave the same on both platforms. Shared code covers them well.
  2. Does it lean on the device? Camera pipelines, Bluetooth accessories, background location, widgets and watch apps are easier and more reliable in native code.
  3. How large is the team after launch? One shared codebase needs fewer people to maintain. Two native apps need two sets of skills.
  4. How soon do you need both platforms? If both stores matter on day one, shared code gets you there sooner.

What we usually suggest

For a first version of a product built from standard screens, we suggest cross-platform. It reaches both stores with one team, and native modules can be added where a feature needs them.

We suggest native when the app is built around the device itself, or when it must match the platform down to the last system gesture.

What does not depend on the choice

Design quality, backend work, analytics and store review take the same effort either way. The framework affects how the screens are written. The rest of the project stays the same size.