Scalability - React Native Architecture
summary
Weeks splits a giant React Native app into an engine that holds the iOS and Android binaries and ~35+ JavaScript-only modules, letting teams ship JS independently and push fixes over the air. About 100 mobile developers work in product teams while one infra team maintains native upgrades and releases a new engine every 2–3 weeks. Startup regressions are traceable per-module, models communicate only through engine contracts, and the approach proves effective at scale.
AI-written summary · about
chapters (10)
- 0:00Start
- 12:28Design an Architecture
- 15:24Separation of Concerns
- 16:39Product Business Logic
- 18:22Infrastructure Team
- 21:20Javascript Libraries
- 32:02Communication between Models
- 32:25Level of Communication
- 33:37Independent Deployment
- 33:47Web Developers
related talks
34mMobile at Scale with React Native & Multi-Module Architecture
35mThe Great Modularization: How We Scaled a 15-Team React Native App Without Losing
32mScaling Mobile Development with React Native
24mScaling teams with Federated Super Apps
45mReact Native: Things we learned the Hard Way
35mBridging the Gap: How to use React Native in existing large native code bases
30mReact Native
33mReact Native At Wix: Building an App for 150 Million Users