Scaling a mobile project across multiple teams and products
summary
A mobile project expanded from 8 to 70 developers across ~20 teams while Android installs grew from 0.5M to 10M and revenue from ~50M to ~850M. They created a central platform team, adopted Feature Module Architecture and a shared design system, moved from offline-first to online-first, and standardized backend contracts using gRPC/protobuf BFF. CI was migrated from Jenkins to GitLab CI with diff-only pipelines, and a three-layer rollout strategy (feature flags + Firebase Remote Config + backend gating) enabled weekly releases, reduced complexity, and improved predictability and observability.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:45Scaling code and architecture
- 12:19Release processes
- 20:47Team communication
- 29:17Modular architecture and design system
- 35:35Database optimization and offline
- 41:34Legacy code and modernization
- 48:10Observability and remote config
- 53:46Summary
- 1:00:30Q&A
related talks
25mFrom 0 to 15 million users
31mA platform approach to scaling mobile app development
39mScaling an Android App from 1 to 100 developers with modularization.
40mScaling Android Apps
35mThe Great Modularization: How We Scaled a 15-Team React Native App Without Losing
40mGrowing Pains: Scaling and Re-architecting Apps Under Fire
39mCreating a Mobile Project for Millions of Users
39mScalability - React Native Architecture