Why Dependency injection with Hilt in depth in Android Kotlin? - Purpose & Use Cases

The Big Idea

Discover how Hilt can save you from tangled code and endless bugs by managing your app's dependencies effortlessly!

The Scenario

Imagine building an Android app where every screen needs to create and manage its own objects like database helpers, network clients, or user settings managers.

You write code to create these objects manually in each screen or class.

The Problem

This manual approach quickly becomes messy and hard to maintain.

Every time you want to change how an object is created, you must update many places.

It's easy to make mistakes like creating multiple copies of the same object or forgetting to clean up resources.

The Solution

Hilt automatically provides the objects your app needs, managing their creation and lifecycle for you.

You just declare what you need, and Hilt injects it where required.

This keeps your code clean, easy to test, and scalable.

Before vs After

✗ Before

val dbHelper = DatabaseHelper(context)
val networkClient = NetworkClient()
val userManager = UserManager(dbHelper, networkClient)

✓ After

@Inject lateinit var userManager: UserManager

// Hilt provides UserManager automatically

What It Enables

It enables building modular, testable, and maintainable Android apps by cleanly managing dependencies across the app.

Real Life Example

In a shopping app, Hilt can provide a single instance of a cart manager to all screens, ensuring the cart data stays consistent without manual wiring.

Key Takeaways

Manual object creation leads to duplicated, hard-to-maintain code.

Hilt automates dependency management, improving code clarity and reliability.

Using Hilt makes your app easier to test and scale.

Practice

1. What is the primary purpose of using @Module and @Provides annotations in Hilt?

easy

A. To tell Hilt how to create and supply dependencies

B. To mark an Android Activity for injection

C. To automatically generate UI components

D. To define navigation between screens

Solution

1. Step 1: Understand the role of @Module

   @Module is used to group methods that provide dependencies to Hilt.

2. Step 2: Understand the role of @Provides

   @Provides annotates methods inside a module to tell Hilt how to create specific dependencies.

3. Final Answer:

   To tell Hilt how to create and supply dependencies -> Option A

4. Quick Check:

   @Module + @Provides = supply dependencies [OK]

Hint: Remember: @Module groups, @Provides creates dependencies [OK]

Common Mistakes:

• Confusing @Module with @AndroidEntryPoint
• Thinking @Provides creates UI elements
• Assuming @Module is for navigation

2. Which of the following is the correct way to inject a dependency into an Android Activity using Hilt?

easy

A. Annotate the Activity with @AndroidEntryPoint and use @Inject on the field

B. Use @Module on the Activity class

C. Call Hilt.inject(this) inside onCreate()

D. Add @Provides on the Activity constructor

Solution

1. Step 1: Identify how to enable injection in Activity

   Hilt requires the Activity to be annotated with @AndroidEntryPoint to generate necessary code.

2. Step 2: Inject dependencies with @Inject

   Fields or constructor parameters annotated with @Inject receive dependencies automatically.

3. Final Answer:

   Annotate the Activity with @AndroidEntryPoint and use @Inject on the field -> Option A

4. Quick Check:

   @AndroidEntryPoint + @Inject field = inject Activity dependency [OK]

Hint: Use @AndroidEntryPoint on Activity, then @Inject fields [OK]

Common Mistakes:

• Trying to use @Module on Activity
• Calling non-existent Hilt.inject() method
• Adding @Provides on constructors

3. Given the following code snippet, what will be the output when MyViewModel is injected?

class MyRepository @Inject constructor() {
    fun getData() = "Data from repository"
}

@HiltViewModel
class MyViewModel @Inject constructor(private val repo: MyRepository) : ViewModel() {
    fun fetch() = repo.getData()
}

medium

A. "fetch() method not found"

B. NullPointerException at runtime

C. Compilation error due to missing @Provides

D. "Data from repository"

Solution

1. Step 1: Understand constructor injection in MyRepository

   MyRepository has an @Inject constructor, so Hilt can create it automatically.

2. Step 2: MyViewModel receives MyRepository via constructor injection

   Hilt injects MyRepository instance into MyViewModel, so calling fetch() returns repo.getData() string.

3. Final Answer:

   "Data from repository" -> Option D

4. Quick Check:

   Constructor injection returns data string [OK]

Hint: If constructor has @Inject, Hilt creates instance automatically [OK]

Common Mistakes:

• Assuming @Provides is always needed
• Expecting runtime null errors with constructor injection
• Confusing method names in ViewModel

4. Identify the error in this Hilt module code:

@Module
@InstallIn(SingletonComponent::class)
object NetworkModule {
    @Provides
    fun provideHttpClient(): OkHttpClient {
        return OkHttpClient()
    }

    @Provides
    fun provideRetrofit(client: OkHttpClient): Retrofit {
        return Retrofit.Builder()
            .client(client)
            .baseUrl("https://api.example.com")
            .build()
    }
}

medium

A. Missing @Singleton annotation on provider methods

B. Retrofit.Builder() requires a converter factory

C. OkHttpClient cannot be provided without parameters

D. NetworkModule should be a class, not an object

Solution

1. Step 1: Review Retrofit.Builder usage

   Retrofit requires a converter factory (like GsonConverterFactory) to parse responses; missing here causes runtime error.

2. Step 2: Check other options for correctness

   @Singleton is optional but recommended; object is valid for modules; OkHttpClient can be created without parameters.

3. Final Answer:

   Retrofit.Builder() requires a converter factory -> Option B

4. Quick Check:

   Retrofit needs converter factory to build properly [OK]

Hint: Retrofit always needs a converter factory to avoid errors [OK]

Common Mistakes:

• Thinking @Singleton is mandatory for all providers
• Confusing object vs class for modules
• Assuming OkHttpClient needs parameters

5. You want to inject two different implementations of an interface Logger using Hilt. How can you distinguish them during injection?

hard

A. Use @Singleton on one implementation and omit on the other

B. Create two separate modules with the same provider method name

C. Use @Named qualifiers with different names on provider methods and injection points

D. Inject both implementations into a list automatically

Solution

1. Step 1: Understand multiple implementations injection

   When multiple bindings exist for the same type, Hilt requires qualifiers to distinguish them.

2. Step 2: Use @Named qualifiers

   Annotate provider methods and injection points with @Named("name") to specify which implementation to inject.

3. Final Answer:

   Use @Named qualifiers with different names on provider methods and injection points -> Option C

4. Quick Check:

   Multiple implementations need @Named qualifiers [OK]

Hint: Use @Named("tag") to differentiate implementations [OK]

Common Mistakes:

• Assuming module separation alone distinguishes implementations
• Using @Singleton to differentiate implementations
• Expecting automatic list injection without setup