metro-di-mobile

Compile-time dependency injection for Kotlin Multiplatform is a technique that assembles type-safe dependency graphs during compilation without runtime reflection. It enables modular, multiplatform architectures across Android and iOS by validating component wiring at build time.

To set up compile-time dependency injection, add the Metro plugin to your Gradle build, declare a dependency graph with @DependencyGraph, and use @Provides and @Inject annotations to wire services across common and platform-specific code sources.

Yes, compile-time dependency injection supports multi-module architectures across Android and iOS. You create platform-specific binding containers in respective source sets to compose modular features like network, data, and UI components.

You handle runtime parameters in a compile-time dependency graph using assisted injection and ComponentContext-based factories. This allows you to pass dynamic runtime values while maintaining compile-time validation for the rest of your component wiring.

No, compile-time dependency injection does not require runtime reflection. It generates type-safe graph assembly code during compilation using the Metro plugin, ensuring all dependency bindings are validated before the application runs.

Compile-time dependency injection requires the Metro plugin and specific annotations like @DependencyGraph and @Provides, adding build-time overhead. Platform-specific bindings must be manually declared in Android and iOS sources to properly assemble cross-platform component graphs.