Modularising the right way
summary
Alibaba runs a multimodule Android app serving millions of users and reports concrete wins: Gradle build cache and parallel builds cut incremental build time (example long full builds like 4m29s), dynamic features plus on-demand delivery shrink APKs and enable feature-by-feature rollout, and Kotlin Multiplatform forces clear module boundaries. Advice includes centralizing dependency versions, extracting shared UI/network libraries, reversing dependencies for dynamic features, and resolving DI and resource conflicts — pragmatic patterns that actually ship.
AI-written summary · about
chapters (26)
- 0:00Intro
- 1:03Motivation
- 2:00Speed up builds
- 3:20Ondemand deployment
- 4:39Simplify development
- 5:38Reduceability
- 6:37Refactor
- 7:46Model
- 8:02Libraries
- 9:50Android Studio
- 11:02Feature modularity
- 11:53Motivation for modularity
- 12:34Topdown approach
- 13:24Topdown diagram
- 14:47Bottomup diagram
- 15:44Dynamic features
- 16:39Modularising step by step
- 17:34Top approach
- 18:29Create a new features module
- 19:42Dynamic features and circular dependencies
- 22:09Navigations
- 23:46Research Conflict
- 24:26Version Conflict
- 25:21Dependency Injection
- 25:51Resources
- 26:40Thank you
related talks
32mBuild a modular Android app architecture
34mIntro to App Modularization
40mModularizing Android Applications
23mModularizing Your App
37mA Complete Journey of Android Modularisation
30mModular Android Development
52mmulti-module Android application
39mScaling an Android App from 1 to 100 developers with modularization.