Scaling Android Apps
summary
Describes moving a monolithic Android app into multi‑modular, semi‑autonomous feature modules so seven+ teams can contribute without breaking master; CI builds master every two hours, runs Espresso + Spoon unit/integration tests and nightly full acceptance tests on an STF device farm, using Calabash for high‑level scenarios and generated Jenkins jobs via Jenkins DSL. Results: backlog falls from ~300 to ~50 tickets, clean builds shrink to minutes and incremental builds to ~30–40s, and releases use code freezes, release branches and tag‑based hotfixes.
AI-written summary · about
chapters (20)
- 0:00Scaling Android apps
- 1:52Startups delay scaling
- 3:17Single team to domain teams
- 6:34Multiple apps and components
- 9:08Release cycles and infra
- 11:17CI pipeline and workflow
- 14:57Testing tools and device farm
- 18:10Human impact and scaling
- 21:04Timeline and conflicts
- 23:35Cross-platform testing
- 26:27Feature code sharing
- 27:54Team size and QA
- 29:00Dependency updates
- 30:44Agile vs scaling
- 33:51Shared resources and theming
- 35:16Hotfixing and branches
- 36:18Freelancers in teams
- 37:45Code style enforcement
- 38:52Code review and sharing
- 39:57Q&A
related talks
37mTackling Android Development at Scale
39mScaling an Android App from 1 to 100 developers with modularization.
52mmulti-module Android application
37mA Complete Journey of Android Modularisation
27mModularising the right way
32mBuild a modular Android app architecture
43mThe Engineering Playbook for Growing Android Teams
40mModularizing Android Applications