hilt-di

To configure Hilt dependency injection for an Android ViewModel, annotate your Application class with @HiltAndroidApp, mark the ViewModel with @HiltViewModel, and define bindings in Modules using @Binds or @Provides to enable proper injection.

The difference between @Binds and @Provides in Hilt modules is that @Binds maps an interface to its implementation with minimal boilerplate, while @Provides contains logic to construct and return dependency instances when instantiation requires explicit setup.

Yes, Hilt dependency injection works with WorkManager integration and testing by using @HiltWorker for worker classes and @HiltAndroidTest to configure automated testing environments, ensuring correct component wiring and scoping.

Your Android component fails to inject dependencies with Hilt typically because the component lacks the @AndroidEntryPoint annotation, or because component lifecycles and scoping rules are mismatched, leading to common compile-time and runtime injection errors.

You cannot use Hilt dependency injection without modifying the base Application class, because annotating it with @HiltAndroidApp is strictly required to initialize the Hilt component hierarchy and generate the underlying Dagger dependency graph.