Using Hilt in a multi module project
summary
Compares Dagger vs Hilt with concrete migration notes and shows Hilt’s real mechanics: modules use the installIn annotation to bind into generated components, Activities and Fragments get injection via AndroidEntryPoint, ViewModels use the Hilt injection helpers, and tests replace bindings with @BindValue or remove production modules with uninstallModules. Explains monolithic generated components, build-speed gains from small feature-only test apps, how Clean Architecture inversion works across Gradle modules, and the current limitation around dynamic feature modules.
AI-written summary · about
chapters (14)
- 0:00Introduction to Hilt
- 1:45Dependency injection basics
- 5:22Dagger vs Hilt
- 8:39Hilt components and modules
- 12:37Android entry points
- 14:45ViewModel injection
- 15:27Monolithic components
- 19:24Entry point annotation
- 20:07Testing with Hilt
- 25:30Multi-module architecture
- 28:06Clean architecture with Hilt
- 32:05Dynamic feature modules
- 33:29Key takeaways
- 34:32Q&A session
related talks
32mUsing Hilt in a Multi-Module Project
25mFully Understanding Dagger Hilt Migration from First Principles
44mHilt: Dependency Injection for the mere mortals
45mDagger Hilt: Live Code Tutorial, Pros and Cons
42m(Unofficial) Guide to App Architecture Guide Vol. 2
22mRex - From Dagger to Dagger Hilt
29mForging the Dagger for the modern Android world
28mThe Lazy (Meta)programmer's Guide to Hilt Extensions