Dagger 2, 2 Years Later
summary
Two years of Dagger 2 adoption produces specific pain points: choice of Dagger Android versus manual injection, whether to use binds vs provides, how to pick scopes and qualifiers, and how to handle late‑bound deps via factories or assisted inject. Practical mitigations include treating components as service locators for simplicity, preferring component dependencies over published modules for testing, avoiding needless interface/implementation pairs, delaying advanced Dagger features, and using default parameters or factories to keep application code simple.
AI-written summary · about
chapters (6)
- 0:00Introduction and setup
- 4:15Two years with Dagger
- 13:37Cost of using Dagger
- 22:45Manual DI vs Dagger
- 32:55Lowering Dagger's initial cost
- 37:15Q&A and summary
related talks
45mDagger 2 - Back to Basics
25mDagger 2 Android : Defeat the Dahaka
30mPowering up Dagger for Less Code and Cleaner Architecture
48mDemystifying Dagger
27mUsing Dagger2 to Keep Android SDK Dependencies Clean
22mDependency Injection in Android using Dagger 2
41mOptimizing Dagger on Android: Developer Workflow and Runtime Performance
15mDagger Party Tricks