React Native
React model, native components
- Shares skills with a React web team
- Large module ecosystem; quality varies
- Some features still need native code
- You already run React on the web
- The app is a standard product experience
Service guide · Cross-platform apps
One codebase is a delivery model, not a discount. What you actually share — and what still needs native work — decides the cost, the risk and the team you should hire.
The short verdict
Choose cross-platform when the product is a standard app experience on both stores and the team benefits from one codebase. Go native when platform-specific hardware, performance or deep OS integration is the product.
Two cross-platform frameworks and one native route. Each is a different skill and maintenance bet.
Select what applies. The output is a scope checklist for partners — not a framework recommendation or an estimate.
Scoping guidance only. Framework choice depends on your team, feature set and release constraints.
The framework decision comes after these four answers, not before.
If one store matters, a responsive web app or a single native app may be the honest answer.
Every hardware or OS-specific item is a native module, an owner and a maintenance cost.
Store accounts, review process and staged rollouts need a named owner inside your organisation.
Ask the partner how your team would maintain the codebase in twelve months.
These are the reasons one-codebase projects lose their advantage.
Early signalA plugin is unmaintained or blocks the next OS release
ResponseInventory modules and name who maintains each
Early signalBoth platforms feel slightly wrong, or one is clearly second class
ResponseDesign for platform conventions, not a lowest common denominator
Early signalReleases stall because nobody owns submissions
ResponseAssign release ownership and a checklist before build
Early signalOnly the vendor can make changes
ResponseRequire documentation, tests and a handover rehearsal
Building one app for iOS and Android from a largely shared codebase, usually with Flutter or React Native, instead of two separate native apps. It suits apps whose screens and workflows are mostly the same on both platforms. Device-specific features still need native work, so plan for some platform-specific code.
Both are established. Flutter uses Dart and draws its own interface; React Native uses JavaScript or TypeScript with native components. Choose by your team’s skills, the native SDKs you depend on and who will maintain the app. See the Flutter and React Native guides.
When the app depends heavily on platform-specific features, demanding graphics or performance, or new operating-system capabilities on release day, or when each platform needs a distinct experience. The native vs cross-platform guide walks through the decision.
Which apps have you shipped and maintained in this framework on both app stores? How do you handle native modules, accessibility and testing on real devices? How are annual operating-system updates handled? Who owns the code, the store accounts and the signing keys?
What this guidance is based on, what it cannot tell you, and where to go next.
An editorial buying guide based on React Native and Flutter documentation. It does not claim one framework is universally faster or cheaper.
Decide, then scope
Shared surface, native gaps and release ownership captured once — then compare partners on the same scope.