Android engineer at Cash App working on Kotlin, Compose, open source, and more
Jake Wharton
Panel: The Future of Dependency Injection in Modern Android
Dependency Injection remains a cornerstone of scalable Android architecture—but as the platform evolves, so do the tools and patterns we rely on. This panel brings together DI experts to discuss the current and future state of DI in Android, from Google’s Hilt and Kotlin-first Koin to community-driven frameworks like Dagger, Anvil, and Metro.
We’ll explore real-world lessons and technical insights across topics such as:
What are the key strengths and weaknesses of current DI frameworks, and how should teams choose the right tool for their architecture and scale?
What are the tradeoffs of using DI at scale, and where do most frameworks begin to show their limitations? How can teams effectively manage complexity, performance, and maintainability as their DI setup grows?
Can Dependency Injection be used for more than just wiring services and repositories? What are some unconventional or creative use cases, and how well do frameworks support them?
What are effective strategies for migrating between DI frameworks, especially in large codebases?
With Kotlin Multiplatform adoption increasing, how can DI be applied across shared and platform-specific code? What are the challenges of building and maintaining multiplatform DI solutions, and what opportunities does this unlock for cross-platform architecture?
What goes into designing and building a DI framework from the ground up? What technical decisions, architectural patterns, and developer experience considerations must be addressed—and where do current solutions still fall short?
Talk Title
The Future of Android…And How to Prepare For It
In this keynote, you'll hear from well-known Android experts about their hot-takes, predictions, wishes and advice about how they expect the Android ecosystem to change and how to best prepare for that future. Join us as they answer the question:
Where do you see Android Development in three years, and how do you think developers should prepare for that future?
After all experts are done making their pitch for the future...its your turn to ask the questions in a rapid-fire Q&A format.