Breaking Down Modularization
summary
Explains a concrete multi‑module layout with layers: application, feature, application‑library, base, core, utility and shows RIBs as the chosen app architecture, Dagger scopes per app/activity/rib, and RX/listeners for wiring; recommends Gradle settings (parallel, configureOnDemand, build cache, Kotlin incremental), uses use implementation not api to avoid rebuild churn, and describes building an AAR SDK with the third‑party fat‑aar workaround by KZong because Android lacks official multi‑module AAR support. Instant apps note: keep modules <4MB.
AI-written summary · about
chapters (13)
- 0:00Introduction to modularization
- 1:16What are modules
- 2:41Why modularize your project
- 5:06Organizing modules by layers
- 8:14Core and utility layers explained
- 9:18Submodules within features
- 9:39App architecture with RIBs
- 11:04Dagger integration with modules
- 13:11Navigation across modules
- 15:16Gradle build optimizations
- 16:58Managing module dependencies
- 17:39API vs implementation dependencies
- 18:41Modular SDK challenges
related talks
40mModularizing Android Applications
32mBuild a modular Android app architecture
05mBy layer or feature? Why not both?! Guide to Android app modularization
17mStructuring modules in an Android app project
27mModularising the right way
01h 12mAbsolute Modularization
23mModularizing Your App
37mA Complete Journey of Android Modularisation