Why Facebook Is Overhauling React Native: Architecture, Goals, and Roadmap

React Native Overview

React Native is currently the most popular cross‑platform development solution, outshining alternatives like Weex with frequent iterations and performance that approaches native applications.

Following the release of React Native 0.56, React engineering manager Sophie Alpert announced a major rewrite to make the framework lighter and better aligned with the evolving JavaScript ecosystem.

Current Usage at Facebook

Facebook heavily relies on React Native for many important projects, including the Marketplace used by 800 million monthly users.

New features such as Blood Donations, Crisis Response, Privacy Shortcuts, and Wellness Checks were all built with React Native, and the Oculus Go VR app’s mobile component is also entirely React Native‑based.

Sophie Alpert emphasizes that React Native is not intended to replace other technologies but to improve itself and inspire ideas like hot‑reloading for non‑JavaScript code.

Architecture

React Native was designed as a bridge between JavaScript and native code, sending JSON messages that describe UI operations (e.g., [["createView", attrs], ["manageChildren", …]]). The system avoids synchronous responses, ensuring all data can be fully serialized to JSON and deserialized back.

This design enables tools such as a Chrome‑style debugger that communicates via WebSocket to run JavaScript asynchronously.

However, the asynchronous bridge and batch bridge have introduced challenges: integrating synchronous native APIs is difficult, and the serialized bridge can cause unnecessary copying and performance overhead, especially for complex integrations with existing native code.

Facebook’s Large‑Scale Refactor

The refactor focuses on three main areas:

Changing the thread model so UI updates can be performed on any thread, pushing low‑priority work off the main thread.

Introducing asynchronous rendering to allow multiple renders and simplify async data handling.

Simplifying the bridge to make native‑JavaScript calls faster, lighter, and easier to debug (e.g., cross‑language stack traces).

These changes aim to enable tighter integration, allowing native navigation, gestures, and components like UICollectionView or RecyclerView to work together without complex hacks.

Roadmap and Vision

Facebook’s vision for React Native includes maintaining a healthy GitHub repository, improving test coverage, ensuring commits follow open‑source guidelines, increasing meaningful community contributions, providing a stable API, and adhering to semantic versioning.

They plan to open‑source JSI to let the community use custom JavaScript VMs, support 64‑bit Android libraries, improve debugging in the new architecture, and enhance support for CocoaPods, Gradle, Maven, and the new Xcode build system.

Community engagement will be strengthened through better documentation, auto‑generated API references, improved release notes, and initiatives that encourage contributor participation.

The majority of this work is expected to be completed within the next year, with some components like the JSI project already open‑sourced.