Integrating React Native with Native Infrastructure
summary
Facebook runs three major React Native apps and hundreds of RN screens and settles on reusing the native navigation stack rather than rebuilding transitions, mapping every screen to a unique URL per screen so native code can open RN roots; routes and nav metadata are co-gen routes JSON read at runtime. Data lives behind a native data fetcher with prefetching to avoid double downloads and speed startup, experiments load at startup for consistency. This approach scales well for full‑screen features and webview conversions but not for tiny embedded banners or full rewrites.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 0:53React Native at Facebook
- 1:30Fully React Native vs Hybrid
- 2:09Navigation
- 7:03Data Loading
- 9:21Experimentation
related talks
33mReact Native: Buy One, Get One Free
23mWhat's New in React Native
45mReact Native: Things we learned the Hard Way
01h 01mReact Native: A Better Way to Do Mobile
25mThe state of React Native
07mFrom Native to React Native
27mBuilding high quality mobile apps with React Native
21mEverywhere: Bringing Into Native Apps