It all starts with navigation
summary
Shows that pushing animation and gesture work off JavaScript into the platform thread fixes jank: the native driver moves Animated from requestAnimationFrame to native, React Native Gesture Handler runs recognition on the UI thread and emits high‑level values like scale and angle, and a native screen container (react-native-screens) keeps only active screens mounted so camera, map and image resources are released. Integrates with react‑navigation, ships in Expo SDK30, and yields visibly faster transitions and lower memory/CPU use.
AI-written summary · about
chapters (11)
- 0:00Introduction and background
- 3:23Early navigation with NavigatorIOS
- 5:31Navigator: First cross-platform solution
- 7:36Animated API and native driver
- 9:47Navigator Experimental and its issues
- 11:54React Native Navigation overview
- 13:43Gestures in navigation and RN Gesture Handler
- 17:17React Navigation and customization
- 19:33View hierarchy and performance impact
- 25:43Introducing Native Screens
- 27:56Demo and performance comparison
related talks
28mReact Native Touch & Gesture
27mDeclarative future of gestures and animations in React Native
35mAnimations and gesture handling in React Native and native languages
22mCan it be done in React Native
30mLiving in an async world of React Native
10mReact Native, your UX superhero
30mMicrointeractions & Animations in React Native: Help users understand the UI
25mJust use platform