React Native

United States · reactnative.dev · 8 vendors

Resilience scores

Technology vendors

Services catalogue

1 service in catalogue across 1 category; runs on 8 sub-vendors.

Insights

Last updated 2026-08-13 · revision 1

8 direct vendors, 150 subvendors

Direct vendors by controlling owner country (sample)

Subvendors by controlling owner country (sample)

Migration Readiness: 9/10

Assessed by AI based on technology stack characteristics (cloud-native vs legacy, containerization, microservices), regulatory environment, data residency requirements, financial stability, and vendor lock-in risks. The score ranges from 0-10, where higher scores indicate better readiness for technology migration.

React Native exhibits high migration readiness. A primary strength is its highly modern, modular, and cross-platform tech stack. The 'React Native New Architecture' (Fabric, TurboModules) represents a significant modernization, moving away from legacy components and enabling better performance and native integration. The framework's support for multiple platforms (Android, iOS, macOS, Windows, Web, VR) demonstrates inherent adaptability and a codebase designed for broad deployment, which simplifies migration efforts. The use of modern languages (JavaScript, TypeScript, Kotlin, Swift, C++) and development practices (e.g., component-based React) further enhances its flexibility. Crucially, the 'Total Vendors: 0' data point indicates a complete absence of direct vendor lock-in, which is a major advantage for any migration scenario. The open-source nature of React Native itself also inherently reduces proprietary lock-in. The main challenges and unknowns for migration readiness stem from the lack of data regarding financial stability ('Revenue Concentration by Product', 'Revenue Concentration by Geography', 'Growth History'), which would be crucial for funding a migration. Similarly, 'Regulatory Environment' and 'Data Residency Requirements' are 'Not specified', which could introduce complexities if specific compliance needs arise during a migration.

Compliance

6 in-scope frameworks identified; showing 3.

COPPA — Partially Compliant

The Meta Open Source Privacy Policy explicitly states that Meta does not knowingly collect or store information from children under 13, and commits to deleting any inadvertently collected data upon notice. This is the standard COPPA compliance posture for a developer-focused website not directed at children. Risk is Low because reactnative.dev is a developer documentation portal not directed at children, and Meta has implemented the required age-based data protection measures.

Evidence: https://opensource.fb.com/legal/privacy/

MIT Open Source License Compliance — Compliant

React Native is distributed under the MIT License, one of the most permissive and widely accepted open-source licenses. The license terms are clearly documented in the GitHub repository and referenced in the Terms of Use. Compliance risk is Low as the MIT license imposes minimal obligations (attribution and license notice preservation) and Meta as the primary maintainer is inherently compliant with its own license terms.

Evidence: https://github.com/facebook/react-native, https://opensource.fb.com/legal/terms/, https://reactnative.dev/

CCPA — Partially Compliant

Meta Platforms, Inc. is headquartered in Menlo Park, California, and the reactnative.dev website collects personal information from California residents. CCPA/CPRA applies to Meta as a large for-profit business that collects personal information from California consumers. The Meta Open Source Privacy Policy references a United States Regional Privacy Notice for US residents, indicating awareness of state privacy obligations. Risk is Medium because Meta has faced regulatory scrutiny under CCPA and similar state laws, and the open-source website's data collection practices (analytics, cookies, identifiers) must comply with California consumer rights (right to know, delete, opt-out of sale/sharing).

Evidence: https://opensource.fb.com/legal/privacy/, https://www.facebook.com/privacy/policies/uso, https://opensource.fb.com/legal/cookie-policy

Financials

Three-year financials

Financial Resilience Score: 8/10

React Native itself is not a company and has no financial statements, revenue, equity, or workforce. Therefore, resilience must be assessed in project-health terms rather than financial metrics. The framework benefits from a deep-pocketed sponsor in Meta Platforms, which has funded the project continuously since 2015 and uses React Native across its own flagship apps including Facebook, Ads Manager, Messenger Desktop, and Meta Horizon. Meta's own financials are extremely strong, with FY2024 revenue of $164.5B, EBIT of $69.4B, and equity of $182.6B, providing ample capacity to continue funding the project. Beyond Meta, React Native has a diversified multi-corporate maintainer base including Microsoft (which maintains React Native Windows and macOS), Expo, Callstack, Software Mansion, and Infinite Red. Broad enterprise adoption by Microsoft, Amazon, Shopify, Coinbase, Discord, Bloomberg, Tesla, PlayStation, Klarna, and the NFL reduces single-sponsor dependency. Active release cadence and strong ecosystem network effects further support long-term sustainability. Key risks include concentration on Meta (if Meta cut open-source spending, capacity would shrink meaningfully), competitive pressure from Google-backed Flutter, absence of a self-sustaining revenue model, and governance risk given that trademark and repo control sit with Meta rather than a neutral foundation.

Key strengths: Deep-pocketed sponsor Meta Platforms funding project since 2015, Meta uses React Native across flagship apps (Facebook, Ads Manager, Messenger Desktop, Meta Horizon), Broad enterprise adoption (Microsoft, Amazon, Shopify, Coinbase, Discord, Bloomberg, Tesla, PlayStation, Klarna, NFL), Multi-corporate maintainer base (Microsoft, Expo, Callstack, Software Mansion, Infinite Red), Active release cadence with regular major releases and React Conf keynotes, Strong ecosystem network effects with thousands of community modules, Top 15 most-starred open-source repository globally (>118,000 GitHub stars)

Risk factors: Concentration on Meta as primary sponsor, Competitive pressure from Google-backed Flutter, No independent revenue model — cannot self-fund if sponsors withdraw, Governance risk — trademark and repo control sit with Meta, not a neutral foundation, Notable historical setback (Airbnb discontinued React Native usage in 2018)

Signed-in users can see whether their own company is exposed to this vendor's disruption, plus the full sub-vendor list and country breakdowns, every in-scope compliance framework plus gaps and next steps, and alerts when any of it changes.

View the full interactive report