What Is React Native?
React Native is an open-source framework from Meta for building native applications for Android, iOS, and other platforms with React. Instead of rendering HTML in a webview, it turns declarative React components into the operating system’s own UI building blocks.
What separates React Native from hybrid wrappers is the rendering layer. Older cross-platform tools drew HTML inside a browser shell. According to the official React Native website, core components such as View, Text, and Image map directly to UIView on iOS and android.view on Android, so users get standard controls, scroll physics, and accessibility.
Meta released React Native in 2015 and maintains it with corporate and community contributors. Because the component model matches React on the web, teams share state management, testing tools, and networking code between mobile and browser.
Partner projects extend the runtime beyond phones and tablets, including React Native Windows, React Native macOS, and React Native Web.
How React Native Works
React Native runs application logic in an embedded JavaScript engine and renders real native views on the device’s main UI thread through a synchronous C++ architecture, so declarative UI code in TypeScript or JavaScript does not block the operating system’s frame rate.
When the app starts, the native host launches the Hermes JavaScript engine, which uses precompiled bytecode to reduce startup time and memory. The React component tree runs there and is reconciled against native view abstractions instead of a browser DOM.
The New Architecture, the only architecture since version 0.82, connects JavaScript and native code through the layers in the table below. It replaced the old asynchronous JSON bridge, so JavaScript can call native code synchronously and layouts are computed in C++ with the Yoga Flexbox engine.
The core library focuses on rendering and platform events and does not include routing or a full set of device APIs. The official documentation therefore recommends starting new apps with a framework such as Expo, which adds file-based routing, build tooling, and dozens of maintained native modules.
| Layer | Role | Runs on |
|---|---|---|
| React component code | UI state, business logic, network calls, and navigation. | JavaScript thread, as Hermes bytecode. |
| JavaScript Interface (JSI) | Exposes C++ objects to JavaScript for synchronous calls without JSON serialization. | C++ bindings shared by the engine and native memory. |
| Fabric renderer | Turns the React tree into C++ layout nodes and mounts native views. | C++ core mounting on the main UI thread. |
| TurboModules | Lazy-loaded access to device APIs such as camera, Bluetooth, and secure storage. | Swift, Objective-C, Kotlin, or Java. |
React Native is the right fit when a roadmap needs feature parity on iOS and Android without two separate platform teams. Engineers who know React become productive on mobile quickly, writing business logic and validation once while users get a real native interface. Production trouble rarely comes from the framework itself: it comes from dozens of unmaintained third-party packages that break when Apple or Google change SDK requirements, and from passing large payloads between threads during scrolling or gestures. We start on the New Architecture, keep native dependencies minimal, run animations on the UI thread, profile on low-end Android devices early, and write small Swift or Kotlin modules when hardware demands it.
Cross-platform native app framework
TypeScript and JavaScript with React
iOS, Android, plus Windows, macOS, and web
Hermes, JSI, Fabric, TurboModules
Years in business
Senior engineers
Projects delivered
What React Native Is Used For
Software teams use React Native to ship customer-facing iOS and Android apps, internal enterprise tools, and companion apps for hardware from one shared codebase.
Commerce and Financial Apps
Retail and fintech companies need fast checkout, biometric login, push notifications, and same-day releases on both stores. Amazon Shopping, Shopify Shop, and Coinbase use React Native in production.
Enterprise Productivity and Messaging
Microsoft uses React Native across Office, Outlook, and Teams, and Discord uses it for mobile. With React Native Windows and macOS, enterprise teams share business logic between workstations and handheld devices.
Hardware Companion and IoT Apps
Tesla, Xbox Game Pass, and the PlayStation App use React Native for companion experiences. Low-level Bluetooth or socket code stays native and is exposed to the React UI for telemetry and device settings.
Media Feeds and Brownfield Features
Bloomberg and Facebook ship content-heavy feeds with React Native, and companies with existing Swift or Kotlin apps embed React Native screens to launch new features without rewriting the whole client.
React Native vs Native Development and Flutter
When comparing React Native vs native development, the trade-off is shared TypeScript velocity with real native views against the full platform access of Swift and Kotlin. Flutter offers a single codebase too, but paints its own UI on a canvas with Dart.
| Criterion | |||
|---|---|---|---|
| Language & ecosystem | TypeScript and JavaScript with React and npm. | Swift for iOS; Kotlin for Android. | Dart and pub.dev. |
| UI rendering | Maps components to native OS views. | Platform frameworks such as SwiftUI and Jetpack Compose. | Draws every pixel with its own engine. |
| Code sharing | High across iOS, Android, web, Windows, and macOS. | None by default; Kotlin Multiplatform can share logic. | UI and logic across mobile, web, and desktop. |
| Platform APIs | Expo modules plus synchronous native bindings for custom APIs. | Immediate access to every new OS API. | Platform channels or FFI bindings. |
| Performance | Near-native UI with some JS engine overhead. | Baseline platform performance and lowest memory use. | Smooth 60/120 fps, with the engine bundled in every app. |
| Team structure | One React and TypeScript team with a mobile lead. | Two platform teams. | One team that needs Dart skills. |
When to Choose React Native
Choose React Native when one product team should deliver iOS and Android apps that look and behave like real platform apps, especially if you already build web frontends or Node.js backends in TypeScript and React. It is the pragmatic choice when most of the app is network-driven screens, forms, lists, authentication, media, and standard device features such as camera, location, biometrics, and push.
When React Native Is Not the Right Fit
React Native is not the right fit for 3D mobile games, augmented reality tools, low-latency audio workstations, or utilities that live in background OS extensions such as VPN tunnels or keyboards. When most of the work is platform-specific Swift and Kotlin against low-level hardware, a cross-platform layer adds build complexity without saving time, and native development is cleaner.
How We Approach React Native Projects
We build React Native apps on a modern foundation with strict typing, focused native modules, and automated release pipelines, as part of our mobile development services.
Expo and the New Architecture
Following official guidance, new projects start on Expo with file-based routing, vetted native modules, and reproducible cloud builds, keeping the generated iOS and Android folders clean. Every dependency is checked for New Architecture support before it is added.
Typed State and Focused Native Modules
Strict TypeScript, separate server and UI state, and shared logic with the web keep the codebase predictable. When a feature needs special hardware, we write a small Swift or Kotlin module instead of pulling in an unmaintained package.
Automated Builds and Releases
Every pull request builds both platforms in CI, runs tests, and is profiled on low-end Android devices. Signing, store submission, and over-the-air updates run from pipelines, never from a developer’s laptop, and secrets stay on the backend.
Sound like the right partner?
Frequently Asked Questions
Direct answers to common architectural and business questions when evaluating React Native.
Is React Native a webview or a real native app?
A real native app. Its core components such as View, Text, and Image create the operating system’s own UI elements, such as UIView on iOS and android.view on Android, instead of HTML in an embedded browser. Users get native scrolling, gestures, and accessibility.
Why does the documentation recommend Expo for new projects?
React Native is a UI library and runtime rather than a full application framework, so it does not include a router or a complete set of device APIs. Expo adds file-based routing, developer tooling, build services, and many maintained native modules, while still letting you write custom native code.
What is the New Architecture (JSI, Fabric, and TurboModules)?
It is React Native’s modern C++ core, which replaced the old asynchronous JSON bridge and has been the only architecture since version 0.82. JSI lets JavaScript call native code synchronously, Fabric mounts native views from a C++ shadow tree, and TurboModules load native APIs only when the app first uses them.
How do you secure a React Native app and protect API keys?
Treat the app binary as untrusted. Never bundle secret API keys in JavaScript or .env files, because they can be extracted from the package. Store session tokens in the iOS Keychain and Android Keystore, use TLS certificate pinning, and route calls that need third-party secrets through your own authenticated backend.
Which major companies use React Native?
Meta created React Native and uses it in Facebook, Ads Manager, and Messenger Desktop. Other users listed in the official showcase or in public engineering posts include Microsoft (Office, Outlook, Teams, Xbox Game Pass), Amazon Shopping, Shopify, Coinbase, Sony’s PlayStation App, Discord, Bloomberg, and Tesla. For cross-platform trade-offs, see our article on cross-platform mobile development.