Transition to Modular Architecture
summary
Migrating a large Android monolith to a feature-based, three-layer setup (library modules, independent feature modules, app container) reduces CI and local feedback time by ~25% and speeds new feature development by ~20% while enabling ~30% team growth. Implementation uses Dagger Android for injected feature contracts, a contextual abstraction pattern (outward/inward navigators, app as orchestrator) and model projections to protect encapsulation. Repo layout is single-repo multi-module with per-module tests and incremental extraction.
AI-written summary · about
chapters (8)
- 0:00Introduction to modular architecture
- 1:35Pain points of monolith architecture
- 4:25Objectives for modular architecture
- 5:29Breaking app into modules
- 8:41Inter-feature interaction
- 12:10Approaches to navigation
- 29:21Approach to modularization
- 32:11Q&A session
related talks
01h 12mRound table. Modularization 2021
40mModularizing Android Applications
32mBuild a modular Android app architecture
37mA Complete Journey of Android Modularisation
35mThe Great Modularization: How We Scaled a 15-Team React Native App Without Losing
39mWhy we failed at modularizing our app. An honest retrospective.
20mStarting Module Separation from New Feature Development
57mModularizing the Monolith