Screens & Routers — The Foundation of Navigation in React Native Apps
summary
Explains how Expo Router’s file-based Expo Router pairs with native primitives from React Native Screens to implement native tabs (released September) that handle gestures, blurs and transitions by coordinating the asynchronous JS and UI threads, sending acknowledgement events and resolving race conditions. Describes categories of bugs found (JS, native, platform), the move to drop legacy architecture in v4.25.0, and an upcoming React Native Screens 5.0 with rewritten native stack, improved async state management, predictive Android back gestures and more reliable view lifecycle events.
AI-written summary · about
chapters (11)
- 0:00Introduction to navigation
- 1:42What is React Native Screens
- 3:03Collaboration between Expo Router and React Native Screens
- 5:32How native navigation works under the hood
- 11:36Creating native tabs implementation
- 13:44Testing and feedback cycle
- 15:28New features in navigation solutions
- 16:52Integration with React Navigation
- 18:39Evolution of React Native Screens
- 20:27React Native Screens 5.0 upcoming changes
- 21:30Q&A and closing remarks
related talks
24mFull Stack React Navigation
29mIt all starts with navigation
45mMobile navigation
53mHow React-Native shapes the way we think about native apps
28mWrite Once, Route Everywhere: File System-based Navigation for Native Apps
32mNavigating React Native Navigation
21mEverywhere: Bringing Into Native Apps
26mIntroduction to Cross‑Platform Development with React Native and Expo