The Engineering Playbook for Growing Android Teams
summary
Company runs ~200 engineers on a single monorepo with ~2 million LOC and ~5,400 Gradle modules across 10 apps, and describes an architecture built on modularization, Dagger-style DI with scoped bags (app / loggedin / activity), codegen via Anvil, and a workflow UI pattern that enforces strong props/outputs. Demo and robots modules cut build times, 45 custom lint rules prevent regressions, CI runs ~14,000 UI tests, PRs take 20–30 minutes, and refactors use a mix of scripted “grind” edits (Timber → new logger) and farmed runbooks.
AI-written summary · about
chapters (9)
- 0:00Scaling Android teams
- 3:58Growing codebases challenges
- 7:12Dependency injection for scaling
- 13:12Modularization for independence
- 20:16UI framework at scale
- 27:40Guardrails for consistency
- 32:17Code ownership and static analysis
- 36:50Large refactors approach
- 41:29Resources and closing
related talks
37mTackling Android Development at Scale
01h 00mAndroid at Scale
40mScaling Android Apps
41mScaling Productivity: How we have improved our dev experience
51mBuilding Effective Teams of Competent, Friendly People
30mModular Android Development
39mScaling an Android App from 1 to 100 developers with modularization.
40mCase Study- How Android Platform @ Reddit learned to stop worrying and embrace DevX