Block the Main Thread
summary
Asynchronous bridge messages cause frame stalls that make touch interactions feel like rubber bands; JavaScript speed isn’t the problem, the async bridge and main-thread blocking is. Uses react-native-gesture-handler and react-native-reanimated to run gestures and complex declarative control flow fully on native, but the native driver only covers limited styles and PanResponder stays async. Implements a production bottom sheet and other interactions, drops into ~300 lines of Swift when needed, and praises Fabric/JSI as the synchronous solution.
AI-written summary · about
chapters (11)
- 0:00Start
- 1:22What Sucks about React Native
- 2:12Personal Finance System
- 4:57Incentives To Use React Native
- 5:24Interactive Animations
- 9:18Animations
- 9:52Animated Module
- 11:14Animation
- 18:47React Native Gesture Handler
- 19:50Custom Custom Activation Criteria
- 22:55React Native Reanimated
related talks
30mLiving in an async world of React Native
28mReact Native Touch & Gesture
10mUnderstanding "Native" in React Native
27mReact Native로 Native한 애니메이션 구현하기
29mPerformance Limitations of React Native and How to Overcome Them
29mIt all starts with navigation
27mDeclarative future of gestures and animations in React Native
17mBreaking the Limits of React Native with Multithreading