React Native team at Facebook publishes its guiding principles
The React Native team at Facebook has published a set of principles describing how it decides what to work on. The team notes that these principles represent the Facebook team specifically, not every stakeholder in the wider community, and that the goal is to be more transparent about how decisions are made and where effort goes.
Native experience
The top priority is matching what users expect from each platform, which is why React Native renders to platform primitives. The team values native look-and-feel over cross-platform consistency. As an example, TextInput renders to a UITextField on iOS, so password managers and keyboard controls work without extra effort, and apps pick up design and behavior changes from new Android and iOS releases.
Performance is treated as part of that native feel. The post points to Hermes, the JavaScript engine Facebook built for React Native on Android to improve start time, and to ongoing architectural work that optimizes the threading model and eases interoperation with native code.
Massive scale
Hundreds of screens in the Facebook app use React Native, and the app runs on a wide range of devices, from recent iPhones to older Android hardware. Problems surfaced at this scale inform projects such as Hermes, Fabric, and TurboModules. Because large teams need gradual adoption, React Native can be introduced one screen at a time, and the team says it will soon support migrating individual native views within an existing native screen.
The post is also explicit about what the team is not currently working on: it does not drive industry adoption of React Native, and it does not actively build solutions for problems it does not encounter at scale. The team says it is proud that partners and core contributors focus on those areas.
Developer velocity
The team aims for code changes to show up in a running app within seconds and says it preserves that fast feedback loop when changing React Native. It also cites the open source package ecosystem and the ability to share business logic across Android, iOS, and the web as ways teams ship faster and reduce silos between platform teams.
Every platform
Referring back to the "Learn once, write anywhere" motto from 2014, the team describes targets including mobile, desktop, web, TV, VR, and game consoles. Rather than building to the lowest common denominator, the focus is on supporting each platform's unique features, such as different input methods. This principle informed the decision to implement the new core architecture in cross-platform C++, and the team is refining the public interface for other platform maintainers, such as Microsoft with Windows and macOS.
Declarative UI
Finally, the team reaffirms React as its programming model. The aim is not identical UI everywhere but exposing each platform's capabilities through the same declarative model. The post argues that unidirectional data flow makes apps easier to understand and notes that the direction of new native Android and iOS frameworks reflects broader industry adoption of declarative UI.
Links
Source: reactnative.dev