guide
React Native apps
How React Native apps share JavaScript UI across iOS and Android, and where native modules and the new architecture matter.
A React Native app is a native iOS app and a native Android app that render a tree of React components. TypeScript is the sensible default. The JavaScript bundle runs in the Hermes engine on both platforms in current templates. UI that maps to native controls can feel at home on each phone. UI that fights the platform, with custom gestures on every row, will feel custom on both, for better or worse.
The new architecture, with Fabric and TurboModules, is the path current releases expect. Older libraries that depend on the legacy bridge need a check before you adopt them. 'It has a lot of stars' is not a compatibility test. Read the issue tracker for the OS versions you must ship, and try the library in a sample binary.
Navigation, safe areas, keyboards, and lists are the everyday bugs. A flat list that cannot recycle will stutter on a mid-range Android phone long before it stutters on a simulator. Test lists with real amounts of data. An empty demo list hides the problem you will have in production.
Native modules are how you reach an API React Native does not wrap. Write them when the product needs them, and keep the surface small: a typed function in, a result or an error out. A module that exposes an entire vendor SDK into JavaScript becomes untestable. Prefer a maintained library when one is healthy. Own the code when the vendor is central to the product.
Over-the-air updates for the JavaScript bundle, through a service or your own pipeline, can ship a UI fix without a store review. They cannot ship a native change, a permission change, or a new entitlement. If you use them, version the native shell and refuse to load a bundle that does not match. A bad bundle is a crash you cannot roll back through the store until the next binary.
CI should produce an iOS archive and an Android bundle from the same commit. Manual archive steps on one developer's laptop will not match the lockfile a week later. Pin Node, pin the React Native version, and treat upgrades as scheduled work because they touch native files.
React Native is a strong fit for teams that already think in React and need both stores. It is a weak fit if nobody wants to open Xcode when a pod breaks. The native folders are not optional expertise. They are smaller than a fully native app, and they are still mandatory.
ClickMasters builds React Native apps and the native edges those apps need. Nothing here is a claim that we timed a particular list against a particular phone for this article.
Document the Node version, the React Native version, and the command that installs pods and Gradle dependencies from a clean checkout. A new teammate should reach a running phone without a private note. Decide whether over-the-air JavaScript updates are allowed. If they are, record which native version they may load and what happens when the versions disagree. If they are not, delete the temptation so a hotfix does not bypass review by accident. Test a long list on a mid-range Android phone and the keyboard on a form on iOS. Those two checks catch the bugs simulators forgive. Keep native module APIs small and typed. A module that dumps a vendor SDK into JavaScript will be the part you cannot upgrade when the OS moves.
Ask for a scoped plan
Send the flows, the platforms, and the systems the app must call. We will reply with what is in the first release and what should wait. This guide is not a quote and not a test report.
Contact ClickMastersRelated guides
- Flutter mobile app development
How a Flutter mobile app is put together in Dart, what stays in the native shells, and how releases reach both stores.
- Kotlin Multiplatform
When Kotlin Multiplatform should share mobile logic while SwiftUI and Compose keep their own interfaces.
- iOS app development
How native iOS apps are planned in Swift and SwiftUI, what App Store review checks, and when iPhone-only is the right scope.
- Android app development
How native Android apps are built with Kotlin, how Play review works, and what to decide about devices, screens, and background work.
- Flutter and React Native
When a shared Flutter or React Native codebase fits, where native code still appears, and how to choose between them.
- Mobile app cost
What actually changes the cost of a mobile app, how to read a range, and what to send so an estimate can be scoped.