Intro to App Modularization
summary
Explains how Android apps split into application, Android library (AAR), and Kotlin/JAR modules, and shows concrete steps that cut full rebuilds from 4–5 minutes to ~1 minute for a feature and to ~15 seconds with a demo app that only compiles one feature. Recommends enabling Gradle cache and parallel builds, using buildSrc with Kotlin DSL to centralize versions, avoiding a generic "base" module, unloading modules in the IDE, and checking KAPT/Dagger incremental builds versus non‑incremental processors like Epoxy.
AI-written summary · about
chapters (13)
- 0:00Introduction to modernization
- 1:49What is modularization
- 2:32Common module types
- 6:22Circular dependencies explained
- 7:26Reasons to modernize apps
- 16:15When to modernize projects
- 17:59Gradle dependency management
- 19:01Modularization approaches
- 21:49Avoid base modules
- 23:13Modularizing by feature
- 27:05Navigating feature modules
- 29:10Demo apps and unloading modules
- 30:13Key learnings and tips
