Future of Dependency Injection
summary
Metro is presented as a new, K2-aware DI tool that compiles far faster than legacy Dagger+Anvil setups and is already published this year; teams report 3‑minute kapt stalls that Metro and Anvil KSP aim to eliminate. Cash App describes an ongoing prod refactor to untangle its graph, large apps hit by thousands of injectables prefer lazy/provider injection by default, K2 forces compiler‑plugin changes so Anvil KSP exists but underperforms, and composition locals act like runtime globals causing invisible errors.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:21Panelists
- 2:29Teaching DI to beginners
- 4:36DI frameworks strengths/weaknesses
- 7:48Future DI migrations
- 10:19Detecting framework limits
- 12:09Why Anvil couldn't continue as before
- 17:08DI for small teams
- 21:32Compose UI service locators
- 26:31Context parameters vs DI
- 31:07Kotlin DI features
- 33:07Lazy injection performance
- 36:17Hilt not discussed
- 38:48Choosing DI for Kotlin Multiplatform projects
- 45:00Closing and Q&A
related talks
40mNavigating Dependency Injection with Metro
40mPlugging into Anvil and powering up your dependency injection
17mKoin vs Dagger (Service Locator vs D.I.)
45mDependency Injection from Zero to Hero
39mInject Basics!
28mDependency Injection You Can Start Today
36mKeynote: Asynchronous Dependency Injection
40mFramework-Free Dependency Injection