Performance Limitations of React Native and How to Overcome Them
summary
React Native’s bottleneck is the serialized bridge so minimize passes over the bridge is the actionable claim. A naïve JS onScroll + setState sends data every frame and stalls under stress. Rewriting the effect as a native wrapper (Objective‑C) runs the math and view updates on the native thread and hits 60fps. A declarative Animated approach that serializes a config to a native driver (the Animated with useNativeDriver pattern) matches native smoothness without rewriting features twice; Wix runs this in production with ~40 devs.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:55Crossplatform
- 5:05Architecture
- 10:39Example
- 15:14Solution
- 19:57Why isnt this good
- 21:07The million dollar question
- 26:23The future
related talks
25mReact Native <3 60FPS -- Improving React Native animations>
30mLiving in an async world of React Native
10mReact Native, your UX superhero
27mReact Native로 Native한 애니메이션 구현하기
24mThe Performance Myths of React Native apps
32mGoing Over The Speed Limit Synchronous Rendering in React Native
46mAnimations in React Native
17mBreaking the Limits of React Native with Multithreading