Structuring modules in an Android app project
summary
Project moves from a flat list to nested folders, a codeowners file assigns specific reviewers, and interface modules plus a runtime service-locator meta file let multiple implementations coexist so apps avoid bundling unused SDKs. Team ships about 90 apps per sprint which drives separate packaging; teams hit module counts near a century and must keep dependency graphs shallow. Enforce rules with a module-graph-assert style tool (modules-graph-assert) and a clear wiki for allowed dependencies.
AI-written summary · about
chapters (9)
- 0:00Introduction to modularization
- 1:51Why modularize your app
- 3:16How many modules is too many
- 4:21Types of modules explained
- 6:50Abstracting module implementations
- 9:59Structuring modules with nesting
- 11:40Assigning module ownership
- 13:27Enforcing module rules
- 16:17Adapting rules over time
related talks
32mBuild a modular Android app architecture
20mBreaking Down Modularization
40mModularizing Android Applications
34mIntro to App Modularization
39mScaling an Android App from 1 to 100 developers with modularization.
52mmulti-module Android application
25mDetangling Your Dependency Graph
40mScaling Android Apps