What is React Native?

React Native is an open-source framework developed by Meta (Facebook) that lets you build native iOS and Android mobile applications using JavaScript or TypeScript with the React paradigm. Unlike hybrid frameworks that wrap a WebView, React Native renders actual native UI components — a <View> becomes a UIView on iOS and an android.view.View on Android.

The key value proposition: one codebase, two native apps. Developers who already know React can apply their knowledge directly to mobile development. Business logic, API calls, state management, and most UI code can be shared between iOS and Android, leaving only platform-specific details to diverge.

Architecture: Legacy Bridge vs New Architecture

Legacy Architecture (Bridge)

The original React Native architecture communicates between the JavaScript thread and the native thread via an asynchronous JSON serialization bridge. Every call from JS to native (and back) must serialize data to JSON, pass it over the bridge, and deserialize on the other side. This works, but introduces latency — particularly painful for high-frequency interactions like gesture-driven animations.

New Architecture (JSI + Fabric + TurboModules)

React Native’s New Architecture, now the default in RN 0.74+, replaces the bridge with three major components:

JSI (JavaScript Interface): A C++ layer that lets JavaScript hold direct references to native objects — no serialization required.
Fabric: The new UI rendering system. UI updates happen synchronously on the native thread, enabling 60fps animations that were previously impossible.
TurboModules: Lazy-loaded native modules that are only initialized when first called, improving startup time significantly.

The result is a React Native that can approach near-native performance for most use cases.

Expo vs Bare Workflow

Expo Managed Workflow

Expo wraps React Native with a pre-configured toolchain. You get:

expo-cli for local development
Expo Go app for instant testing on device (no build required)
EAS Build for cloud-based iOS/Android builds (no Mac required for iOS)
60+ pre-built SDK modules (Camera, Location, Notifications, etc.)
OTA (over-the-air) updates via EAS Update

The managed workflow is ideal for most new projects, especially if you want to avoid Xcode and Android Studio complexity.

Bare Workflow

The bare workflow gives you full access to the native iOS and Android project files alongside your React Native code. You lose some Expo convenience but gain complete control — useful when you need a native module not available in the Expo SDK or need to customize build configurations.

Key Libraries

Category	Library	Notes
Navigation	React Navigation v6	Industry standard, Stack/Tab/Drawer
UI Components	React Native Paper	Material Design 3 components
State Management	Zustand / Redux Toolkit	Zustand for simplicity, RTK for complex state
Storage	MMKV	10x faster than AsyncStorage
Images	react-native-fast-image	Better caching than default Image
Animations	Reanimated 3	Runs on UI thread, 60fps guaranteed
Forms	React Hook Form	Same library as web React

Performance Tips

Use Reanimated 3 for any animation that runs continuously — it executes on the native UI thread, not the JS thread.
Enable Hermes (enabled by default since RN 0.70) — Meta’s JavaScript engine optimized for React Native.
Use FlashList instead of FlatList for long lists — 10x faster rendering for large datasets.
Memoize aggressively with React.memo, useMemo, and useCallback — the JS thread is single-threaded.
Enable the New Architecture — migrate to JSI/Fabric for any performance-critical app.

When to Choose React Native vs Flutter vs Expo

Factor	React Native	Flutter	Expo
Team background	Web/React developers	No existing preference	Fastest startup
Performance needs	Good (New Arch)	Excellent (Impeller)	Good
Native feel	Excellent (real native)	Good (custom renderer)	Excellent
Setup complexity	Medium	Medium	Low
Ecosystem size	Very large (npm)	Growing (pub.dev)	Medium
OTA updates	Via EAS Update	Limited	First-class

React Native is the default choice for teams coming from a web/React background. If pixel-perfect custom UI with guaranteed 60fps animations is the priority, Flutter is worth the Dart learning curve. For the fastest possible start with least friction, Expo’s managed workflow is unbeatable.

Getting Started

# With Expo (recommended)
npx create-expo-app MyApp --template

# Bare React Native
npx @react-native-community/cli init MyApp

React Native’s combination of a massive ecosystem, familiar React patterns, Expo’s managed infrastructure, and the performance gains of the New Architecture make it the most practical choice for most cross-platform mobile projects in 2026.

Concrete Use Case: Shipping a B2C Consumer App to iOS and Android from a Web React Team

A startup with a React/Next.js web team of six engineers is tasked with shipping a consumer mobile app on both iOS and Android within three months. Hiring native iOS and Android specialists is budget-prohibitive; the team has no Swift or Kotlin experience. They choose Expo’s managed workflow with React Native, betting that the team’s React knowledge transfers directly.

The team bootstraps with npx create-expo-app using the TypeScript template, which provides Expo Router (file-based navigation), EAS Build for cloud-based binary compilation (critical — nobody has a macOS machine for iOS builds), and EAS Update for over-the-air hotfixes between App Store releases. Navigation uses React Navigation v6 with a Stack + BottomTab hybrid pattern the team finds immediately familiar from web routing. State management uses Zustand (same library the web team uses) for global state and React Query for API caching — zero new libraries to learn for server state. For the core smooth-scroll feed feature, they use FlashList instead of FlatList after benchmarking, and Reanimated 3 for gesture-driven like-button animations that run at 60fps on the native UI thread.

The app ships to both App Store and Google Play in 11 weeks. EAS Build handles all binary compilation in the cloud — iOS and Android builds run in parallel and upload directly to TestFlight and Google Play Internal Testing without any local Xcode/Android Studio environment. When a critical bug surfaces in the onboarding flow two days after launch, the team deploys a fix via EAS Update in 20 minutes: an over-the-air JavaScript bundle push that reaches active users without an App Store review cycle. Code sharing between web and mobile reaches approximately 65% — business logic, API integration, Zod validation schemas, and utility functions are shared via a packages/core workspace; only navigation and UI components are platform-specific. The engineering cost is two months of team productivity on new technology versus the 12+ months required to hire and onboard dedicated iOS/Android engineers.

When to Use React Native

Use React Native when:

Your development team has existing React and JavaScript/TypeScript skills and you want to apply that knowledge directly to mobile without learning Swift, Kotlin, or Dart
You need to ship to both iOS and Android from a single codebase and can accept minor platform-specific divergences
You want a large, mature ecosystem — thousands of npm packages, strong community support, Meta’s long-term investment, and Expo’s managed infrastructure
Time-to-market is critical and you want the fastest path from a web React team to published mobile apps

When NOT to use React Native:

Your app requires extremely complex, custom animations at 60fps with pixel-perfect rendering — Flutter’s Impeller rendering engine has a consistent edge here, especially for game-like interfaces
Your app needs deep native platform integration with platform-specific APIs (ARKit, HealthKit, advanced Bluetooth) where native modules add significant complexity
Your team has no JavaScript/TypeScript experience and is starting fresh — Flutter’s Dart is equally approachable and Flutter’s tooling may be simpler for a team with no existing JS ecosystem investment

React Native — Cross-Platform Mobile with JavaScript/TypeScript

✅ Pros

⚠️ Cons