Dagger Reflect - The circle from runtime to compile time and back to runtime
summary
Dagger Reflect replaces Dagger’s heavy generated code with a reflection runtime that cuts annotation‑processing time and speeds local builds: measured average builds drop from 58s to 45s — saves 23% on builds — while the reflect compiler runs in about 60 ms compiler run. A small Gradle plugin called Delect Gradle plugin automates swapping dagger dependencies; artifacts are on Maven Central (dagger‑reflect 0.10, Delect 0.1.0). Some Dagger features and error messages differ and app startup can be slower due to reflection.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:58History of DI frameworks
- 4:07Problem with Dagger builds
- 4:27What is Dagger Reflect
- 6:11How reflection works
- 10:30Developing Dagger Reflect
- 15:12Using Dagger Reflect
- 18:27Delect Gradle plugin
- 20:14Build speed improvements
- 22:20Current state and future
- 24:29Usage at SoundCloud
- 25:54Build time tracking
- 27:40Impact on local builds
- 28:00Closing and thanks
related talks
59mComparing DI frameworks & internals
41mOptimizing Dagger on Android: Developer Workflow and Runtime Performance
15mDagger Party Tricks
48mDemystifying Dagger
30mPowering up Dagger for Less Code and Cleaner Architecture
38mDagger 2, 2 Years Later
45mDagger 2 - Back to Basics
25mDagger 2 Android : Defeat the Dahaka