Dagger 2 Android : Defeat the Dahaka
summary
Explains how Dagger 2 works by examining the compile‑time generated classes (Providers, Factories, Builders, MemberInjectors, DoubleCheck, Lazy, Producers) to clarify the relationships between Modules and Components. Shows strategies for managing complexity in Android projects—using scopes, dependent components, subcomponents—and how to transition to Dagger Android more intelligently.
AI-written summary · about
chapters (15)
- 0:00Start
- 3:29SCOPES FACE OF THE DAHAKA
- 4:06@SINGLETON EXAMPLE
- 4:29DEPENDENCY WITH SCOPE
- 6:16DEPENDENCY WITHOUT SCOPE
- 7:24@REUSABLE
- 8:51GOD APP MODULE
- 10:04COMPONENT DEPENDENCIES
- 11:53DAHAKA APPLICATION
- 12:30USER MANAGER
- 13:05DAGGER USER COMPONENT
- 13:22SUB COMPONENTS
- 13:45DAGGER APP COMPONENT
- 15:05DAGGER 2
- 24:02CUT SCENES
related talks
38mDagger 2, 2 Years Later
45mDagger 2 - Back to Basics
29mForging the Dagger for the modern Android world
48mDemystifying Dagger
41mA (K)night with Dagger - Slicing problems of newbies
27mUsing Dagger2 to Keep Android SDK Dependencies Clean
30mPowering up Dagger for Less Code and Cleaner Architecture
41mOptimizing Dagger on Android: Developer Workflow and Runtime Performance