React Native at Uber Eats - handling scale and complexity
summary
React Native powers a tablet restaurant app that runs on iOS, Android and web with 93% code sharing and serves 120,000 weekly active restaurants across 35+ countries; the team uses Flow, Redux-saga, Lahi for audio, React Native to Web, Fabricator and Jenkins, and builds a custom code-push with three bundles that validates and rolls back JS updates. A hard-to-find production problem turns out to be a memory leak from animation callbacks that drives monitoring and alerting changes to prevent day‑long device outages.
AI-written summary · about
chapters (15)
- 0:00Introduction and background
- 2:58Restaurant app evolution
- 5:03Live app demo
- 7:57Scale and platform choice
- 9:44Business impact and growth
- 10:26Migration to React Native
- 11:30Native integration strategy
- 12:32Code push and deployment
- 14:39State management with Redux
- 15:44Peripheral device support
- 17:09Debugging memory leaks
- 19:56Native module integrations
- 21:41Key learnings and team fit
- 23:47Integration with Uber infrastructure
- 24:11Q&A session
related talks
28mShould I use React Native too?
25mReact Native at Traveloka
17mDispatches from React Native
51mRapid App Development With React Native: Lessons Learned at NSB
42mLessons Learned from React Native at Airbnb
10mReact Native at Eaze Marijuana Delivered
45mReact Native: Things we learned the Hard Way
44mBest Practices to Build Scalable React Native Apps
