android-dependency-injection

Configuring Android dependency injection for multi-module architectures requires structuring module definitions and scopes to create clean DI surfaces. This skill guides you through organizing modules for Hilt, Koin, and Metro to reduce boilerplate and decouple dependencies.

Comparing Hilt, Koin, and Metro involves evaluating each framework's setup, module organization, and testing patterns for your specific project needs. This skill provides framework selection guidance to help you choose the right DI solution for single-project or multi-module apps.

Migrating between Android dependency injection frameworks requires mapping existing module definitions and scopes to the new framework's structure. This skill demonstrates migration scenarios and setup steps to transition between Hilt, Koin, and Metro while maintaining testability.

Yes, you can write tests with injected dependencies in Android using this skill. It demonstrates specific testing patterns for Hilt, Koin, and Metro, helping you implement test strategies that reduce tight coupling and improve testability across your project.

Yes, configuring Android dependency injection requires existing knowledge of Kotlin and Android project structure. The skill applies this prerequisite knowledge to demonstrate module definitions, scopes, and framework setup for single-project apps and multi-module architectures.