React Native Core Contributor Summit 2024 recap published
The React Native blog has published a recap of the 2024 Core Contributor Summit, the annual meeting where community core contributors and the React Native team discuss the project's direction. The Summit is usually held a day before React Universe Conf (formerly React Native EU) at Callstack HQ in Wrocław; in 2024 it ran for two consecutive days to allow more unstructured time.
Releases
The Core Team stressed the value of outside contributors in releases and of nightly releases, which help Out-of-Tree platforms like React Native visionOS, library maintainers (Reanimated) and frameworks (Expo). Participants were split on release frequency: some wanted faster fixes, others worried about the impact on 3rd party libraries and upgrades. Ideas to reduce unintentional breaking changes and improve compatibility communication were also brainstormed.
What's next after the New Architecture?
Topics included web compatibility, with React Strict DOM to be treated as a temporary polyfill while the Xplat team builds cross-platform functionality into core; stabilizing the core API; and old architecture support, where the team confirmed new React 19 features based on concurrent rendering won't work in the old architecture. Other items covered better documentation for library authors choosing between TurboModules, ExpoModules and NitroModules, updated brownfield docs for Android and iOS (since published), and the core Metro team being open to merging the Expo team's tree-shaking work for Metro web.
Web APIs for Native Modules
This session discussed Microsoft's RFC to bring a subset of Web APIs to React Native. Microsoft has identified around 200 essential Web APIs that could be implemented first for iOS, Android, Windows and macOS. Open questions include API governance, divergence from W3C specifications, and avoiding bundling unnecessary modules. Microsoft together with Callstack could refine the RFC and produce a proof of concept for a smaller number of APIs.
LeanCore 2.0
Building on the 2019 Lean Core initiative, the session looked at reducing React Native's component and API surface, including platform-specific props such as android_disableSound and android_ripple on Pressable. A group of core contributors will look at collecting more telemetry, assess community alternatives and prepare an RFC.
Nitro Modules
Participants discussed trade-offs between Marc Rousavy's Nitro Modules, which use experimental C++ Swift Interop, and TurboModules, along with the potential for upstreaming some Nitro Modules improvements into React Native Core.
Out-of-Tree Platforms & CocoaPods
Platform maintainers discussed the lack of guidelines for creating and maintaining Out-of-Tree platforms. With CocoaPods having moved to maintenance mode, alternatives for managing native dependencies and possible migration paths were also discussed.
React Native on Desktop
Steven and Saad from Microsoft, maintainers of react-native-windows and react-native-macos, gathered feedback on increasing desktop adoption, including ideas such as a dedicated workflow in Visual Studio, exposing desktop as part of Nx, and supporting Expo. Software Mansion is working on desktop support for its most popular modules, such as React Native Screens, Gesture Handler and Reanimated.
Links
Source: reactnative.dev