The Great Modularization: How We Scaled a 15-Team React Native App Without Losing
summary
A concrete postmortem: a modular React Native app grows from 3–5 to 15+ teams using shared libraries, a product template generator, local isolated apps and a debug screen to develop modules in parallel; a backend-driven JSON CMS implements server-driven UI so marketing and legal push text and banners in minutes; a platform-as-product shifts goals toward a dev portal docs, release train and automation. It works enough to scale but keeps being iterative—poor early documentation and dynamic-component constraints create ongoing tradeoffs.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:46Modular architecture for speed
- 9:04Shared libraries setup
- 12:18Server-driven UI
- 18:43Bruno to CMS for UI
- 21:36Documentation pain point
- 23:43Platform-as-product mindset
- 26:55Release trains and autonomy
- 29:30Lessons learned
- 32:47Iterative process
- 34:53Q&A
related talks
49mScalable Best Practices for Your Development Team
32mScaling Mobile Development with React Native
39mScalability - React Native Architecture
34mMobile at Scale with React Native & Multi-Module Architecture
41mYou Keep Using That Word, I Don’t Think It Means What You Think
25mGoing Native
24mScaling teams with Federated Super Apps
44mApplications instead of libraries: Micro frontends implemented through module federation