Tackling Android Development at Scale
summary
Android team grows from four to twenty-seven engineers in a year and a half and hits 500% growth, forcing changes to architecture, workflow and tooling. Monolith splits into ~100 modules then consolidates to standalone feature modules; dependency injection uses compile‑time checks; Retrofit/OKHttp transitive deps force two‑year legacy lock. Build time climbs from 1.5 to 7 minutes then drops after upgrades and a feature launcher — 15s builds trick. Testing rises from ~200 to 8,000 unit tests, adds 400 Espresso UI tests and raises automated regression coverage from ~10% to ~50%.
AI-written summary · about
chapters (5)
- 0:00Introduction and growth journey
- 10:46Code architecture principles
- 20:01Modularization strategy
- 30:45Design systems and testing
- 36:47Q&A and closing
related talks
43mThe Engineering Playbook for Growing Android Teams
40mScaling Android Apps
39mScaling an Android App from 1 to 100 developers with modularization.
52mmulti-module Android application
40mCase Study- How Android Platform @ Reddit learned to stop worrying and embrace DevX
17mBest Practises for Android Development as a Daily Business
41mBuilding Mobile Apps At Scale
40mSubito, Android Development at Scale