A framework for building native applications using React
126.2k
Stars
25.2k
Forks
1k
Open issues
30
Contributors
AI Analysis
React Native is a cross-platform mobile application framework that allows developers to build native iOS and Android apps using React and JavaScript, sharing code across platforms while accessing native UI controls. It best serves mobile developers who already know React and want to avoid maintaining separate native codebases per platform. It is not intended for web-only developers, desktop-first use cases, or teams requiring deep platform-specific performance optimizations beyond what a Java...
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
React Native lets JavaScript developers ship native iOS and Android apps from a shared codebase
React Native is Meta's open-source framework that allows developers to build native mobile applications for iOS and Android using React and JavaScript/TypeScript. It renders actual native UI components rather than WebViews, distinguishing it from hybrid approaches. Its primary audience is web developers with React experience who need to ship mobile apps without learning Swift/Kotlin from scratch, as well as organizations wanting to share logic across platforms. With 126k GitHub stars, weekly npm downloads consistently in the tens of millions, and adoption at companies like Meta, Microsoft, Shopify, and Coinbase, it is one of the most widely deployed cross-platform mobile frameworks in existence.
Originated from an internal Meta hackathon in 2013, open-sourced in 2015. The architecture underwent a major multi-year rewrite ('New Architecture' with JSI, Fabric renderer, and TurboModules) that reached stable status around 2024, addressing long-standing performance and interop limitations.
Early growth was driven by Meta's backing and the large existing React/JavaScript developer pool. The 2018-2021 period saw some turbulence as Airbnb and others publicly abandoned it, but Meta's continued investment, the New Architecture rollout, and Expo's maturation as a managed workflow reignited confidence. Growth is now mature and steady rather than explosive — 62 stars in 7 days reflects a stable, established project, not a declining one.
Extensively documented production usage: Meta (Facebook, Instagram), Microsoft (via react-native-windows), Shopify, Coinbase, and hundreds of others are cited in the official showcase. npm download counts are publicly verifiable at tens of millions per week. Stack Overflow developer surveys consistently place it among top mobile frameworks. Expo, which builds on React Native, reports millions of apps built on its platform.
Likely a hybrid C++/JavaScript architecture. The New Architecture introduces JSI (JavaScript Interface) for synchronous native-to-JS communication, Fabric as the new concurrent-aware renderer, and TurboModules for lazy-loaded native modules. The core is written in C++ for cross-platform portability, with platform-specific wrappers in Objective-C/Swift (iOS) and Kotlin/Java (Android). The JavaScript layer runs in Hermes, Meta's optimized JS engine.
Not documented in README, but the project has a known CI pipeline and contributing guide that references testing requirements for PRs. Actual coverage metrics are not surfaced in the README excerpt.
Extremely active. Last push was 2026-06-26, the same day as the evaluation date. With 25,000+ forks and Meta as primary maintainer alongside a substantial contributor community, maintenance signals are strong. Regular versioned releases, a dedicated releases discussion repo, and an active roadmap all indicate sustained, organized maintenance.
ADOPT IF: your team has React/JavaScript experience and needs to ship on both iOS and Android without building separate native codebases, or you are integrating mobile into an existing React web product. AVOID IF: your app demands the absolute latest platform APIs, deeply platform-specific UX, or you have a native-expert team where the abstraction layer adds cost without benefit. MONITOR IF: you are currently on the old bridge architecture and have not yet migrated to the New Architecture, as the ecosystem is mid-transition and some third-party libraries lag behind.
Independent dimensions
Mainstream potential
8/10
Technical importance
9/10
Adoption evidence
10/10
- The New Architecture migration (JSI, Fabric, TurboModules) is a significant breaking change for existing libraries; third-party ecosystem completeness varies and teams may encounter unmigrated dependencies.
- iOS development still requires a macOS machine, creating an uneven developer experience for teams on other operating systems despite Expo Cloud Build partially mitigating this.
- Flutter continues to gain market share and mindshare, particularly in greenfield projects, which may gradually reduce React Native's talent pool and third-party library investment over time.
- Meta's organizational priorities could shift, as has happened historically with other Meta open-source projects; community governance partially mitigates this but Meta still controls core architecture decisions.
- Performance-sensitive applications (e.g., complex animations, real-time graphics) may still hit ceiling issues that require dropping down to native modules, increasing complexity and partially negating cross-platform benefits.
React Native will remain a top-two cross-platform mobile choice for the foreseeable future, consolidating around the New Architecture and Expo-based workflows, with Flutter as its primary long-term competitive pressure.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://reactnative.dev
- Language
- C++
- License
- MIT
- Last updated
- 11h ago
- Created
- 140mo ago
- Analyzed with
- anthropic/claude-sonnet-4-6
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
Android: Scroll View Stretch Effect Inconsistency
Pressability silently drops presses when measure() disagrees with the native hit test (Fabric, natively repositioned views)
[iOS][New Arch] Text without numberOfLines clips the last word when the final line is a single short "orphan" token (NSLineBreakByClipping)
iOS: NSRangeException crash drawing truncated <Text> when the ellipsis boundary splits a composed character cluster (processTruncatedAttributedText)
iOS precompiled binaries in React Native 0.84.1 ignore custom Metro ports
Similar repos
microsoft/react-native-windows
React Native for Windows enables developers to build native Windows...
react-native-elements/react-native-elements
React Native Elements is a cross-platform UI component library for React Native...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
react/react-native
this
|
126.2k | +34 | C++ | 9/10 | 11h ago |
|
microsoft/react-native-windows
|
17.3k | — | C++ | 8/10 | 1d ago |
|
react/react
|
246.4k | — | JavaScript | 10/10 | 11h ago |
|
react-native-elements/react-native-elements
|
25.9k | — | MDX | 8/10 | 2mo ago |
 expo/expo
|
50.6k | — | TypeScript | 9/10 | -27 min ago |
 react-navigation/react-navigation
|
24.5k | — | TypeScript | 8/10 | 15h ago |
Flutter uses its own Skia/Impeller rendering engine rather than native components, offering more visual consistency across platforms at the cost of native look-and-feel fidelity. Flutter has grown rapidly and now competes directly for the same developer audience. React Native has a larger existing JavaScript talent pool to draw from; Flutter requires Dart. Both are viable production choices.
Expo is a managed layer on top of React Native, not a direct competitor. It significantly reduces setup friction and provides a cloud build service. Many new React Native projects start with Expo. Expo's growth reinforces React Native adoption rather than displacing it.
Ionic/Capacitor uses WebViews to render HTML/CSS rather than native components. It offers better web code reuse but generally lower performance and less native fidelity than React Native. Targets developers prioritizing web compatibility over native feel.
Full native development offers maximum performance, platform API access, and toolchain support. React Native may still require native modules for advanced platform features, and the bridging layer adds complexity. Teams with existing native expertise and platform-specific UX requirements may find the overhead of React Native's abstraction not worth the cross-platform benefit.
An extension of React Native to Windows and macOS desktop targets, maintained by Microsoft. It is complementary rather than competitive — it broadens React Native's platform reach. Adoption is narrower and the maintenance burden falls primarily on Microsoft.
