Fast by Default: Performance Starts with State
summary
Claim: app slowness comes from state placement not lists; a benchmark shows re-rendering at the root is 10× slower than updating a leaf. Uses and compares FlatList FlashList Legend List plus Redux Zustand Jotai MobX and recommends Legend State for fine‑grained observables that target single-node updates. Built features include tiny reactive wrappers, two‑way bindings, undo/redo and an offline first sync engine. Results: much lower CPU, far fewer reconciliations, and production use of a 3.0 beta.
AI-written summary · about
chapters (10)
- 0:00Performance challenges
- 0:56State and re-rendering
- 3:07Benchmarking performance
- 4:30Adopting state libraries
- 5:11Fine-grained reactivity
- 6:15The origin of Legend State
- 7:16How Legend State works
- 10:12Comparing state solutions
- 12:13Advanced features and sync
- 17:42Conclusion
related talks
20mHow to Build the Fastest Apps: Break the Rules
23mFlashList – make your lists faster now
39mDefault to performance
26mReact: Lifting state up is killing your app
24mThe Performance Myths of React Native apps
41mThe Battle of State Management in modern frontend applications
31mThe performance myths of React Native
21mMaking Your React Apps Perform At Scale