Structuring modules in an Android app project
summary
Empirical rules and tools decide: a real codebase has 150+ modules and publishes stable modules to Nexus so developers avoid rebuilding everything, yielding much faster iteration across 100+ white‑label apps per sprint. Interface modules plus a service‑loader fragment factory let multiple implementations coexist without bundling unused analytics. Enforced ownership via CODEOWNERS and automated checks — module graph & dependency analysis — reveal deep dependency chains, unused and transitive deps, and improve build speed.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:07Purpose of modularization
- 3:30Managing many modules
- 4:54Types of modularization
- 6:19Improving abstraction with interfaces
- 8:44Dynamic features with service loader
- 11:12Nested packages in modules
- 13:18Enforcing module ownership
- 14:42Build speed with Nexus dependencies
- 17:55Tools for module dependencies
- 20:22Adapting to team needs
- 21:03Q&A
related talks
39mScaling an Android App from 1 to 100 developers with modularization.
51mMultimodule Project Architecture
17mBest Practises for Android Development as a Daily Business
42mBuilding Scalable Mobile Projects: Fast Builds, High Reusability and Clear Ownership
46mCode Refactoring The Solid Way
35mTools of the Trade
49mMobile Developer Productivity Panel
33mTools of the Trade