How we made our app 80% faster, a data structure story
summary
An 80% app speedup comes from replacing an O(n) permissions lookup with a keyed object and measuring the impact with DataDog RUM instrumentation. App originally uses Redux + redux-persist so every task update triggers redux-persist stringifying huge state across the bridge; WatermelonDB was trialed but proved heavy and buggy. After the permission restructure, selectors drop ~92%, reducers ~90% and sagas ~64% in latency, biggest wins on low-end devices.
AI-written summary · about
chapters (5)
- 0:00Introduction and context
- 6:10Slow app and unknown causes
- 16:27Failed attempts and lessons learned
- 22:0680% performance improvement revealed
- 22:49Key takeaways and closing
related talks
51mQ&A Session
01h 00mArchitecting Data-Driven Apps for UX Success
32mA Tale of Two Architectures
29mStructure Your App's Story With Sagas and Selectors
39mPerformance Does Matter - Making Your React-Native App Fast
32mStructuring Your App’s Story With Sagas and Selectors
36mReact + Redux: Performance & Scalability
20mOffline-First React Native: Designing for production