Forging the Dagger for the modern Android world
summary
Shows how to use Dagger with modular apps to cut build time and boilerplate, with concrete tactics: avoid Dagger Android and avoid subcomponents, prefer component dependencies, keep the app module mostly empty. Demonstrates dynamic feature vs library tradeoffs, explains when generated code forces full recompiles, reports incremental edit–compile cycles down to ~15–20 seconds on a new feature, and cites App Bundles shrinking APK size from ~24 MB to ~11–15 MB.
AI-written summary · about
chapters (20)
- 0:00Intro
- 1:01Dependency Inversion of control
- 2:50Dagger is not the only solution
- 4:10Dagger. yes or no?
- 6:08Advices to avoid boilerplate
- 7:03How build time became a problem
- 8:22How we can improve it
- 9:33Why should I modularise?
- 11:05First steps into modularisation
- 11:58Feature modules
- 12:30What do you want your module to be?
- 18:15Modularising by libraries (in reality)
- 19:28Modularising with dynamic features
- 21:09In the end...
- 22:24You can use Dagger Android but...
- 23:22Dagger in a dynamic feature
- 24:41Dagger in a library feature
- 25:59Dagger in dynamic features vs libraries
- 26:26Tomorrow at 1.40 pm
- 27:11An example of a modularised app
related talks
32mBuild a modular Android app architecture
35mArchitecture for App Bundles
40mModularizing Android Applications
25mDagger 2 Android : Defeat the Dahaka
34mIntro to App Modularization
45mDagger 2 - Back to Basics
41mA (K)night with Dagger - Slicing problems of newbies
41mOptimizing Dagger on Android: Developer Workflow and Runtime Performance