Demystifying Dagger
summary
Asserts Dagger remains useful and explains how it works under the hood: annotation processing generates Java factories like CrashReporter_Factory and members injectors, each implementing JSR-330 Provider<T>; modules produce provider classes (e.g. CrashModule_provideBackend_factory), qualifiers disambiguate primitives, components/subcomponents form a directed acyclic graph, and scoping wraps providers to cache instances. Mentions using Anvil/Hilt to merge modular contributions into a generated DaggerAppComponent and having used Dagger for at least a decade.
AI-written summary · about
chapters (12)
- 0:00Introduction to Dagger
- 1:56Dependency injection basics
- 5:53JSR 330 standard
- 8:23Constructor injection
- 12:36Member injection
- 18:15Provider injection
- 25:37Qualifiers in Dagger
- 29:40Graph components
- 34:03Component scopes
- 40:27Subcomponents explained
- 44:01Dagger with Hilt and Anvil
- 47:57Q&A
related talks
30mPowering up Dagger for Less Code and Cleaner Architecture
45mDagger 2 - Back to Basics
25mDagger 2 Android : Defeat the Dahaka
38mDagger 2, 2 Years Later
40mFundamentals of Dependency Injection
29mForging the Dagger for the modern Android world
15mDagger Party Tricks
41mA (K)night with Dagger - Slicing problems of newbies