Dependency injection with Hilt in Android Kotlin - Build, Publish & Deploy

Build & Publish - Dependency injection with Hilt

Performance Impact

Using Hilt for dependency injection helps your app start faster by managing object creation efficiently. It reduces redundant object creation, which saves memory and CPU. This leads to smoother UI rendering and better battery life because your app avoids unnecessary work during runtime.

Optimization Tips

To keep your app running at 60fps, avoid injecting heavy objects directly into UI components. Instead, inject lightweight interfaces or use lazy injection to create objects only when needed. Also, scope your dependencies properly (e.g., Singleton, ActivityScoped) to reuse instances and reduce memory overhead.

App Size Impact

Adding Hilt increases your app size slightly due to generated code and annotations. Typically, this adds a few hundred kilobytes, which is small compared to the benefits. To minimize size, enable code shrinking (ProGuard/R8) which removes unused code and optimizes the final APK or AAB.

iOS vs Android Differences

Hilt is specific to Android and Kotlin. iOS uses different dependency injection patterns, often manual or with Swift frameworks like Resolver or Needle. Android requires annotation processing for Hilt, while iOS uses compile-time Swift features. Understanding these platform differences helps when developing cross-platform apps.

Store Review Guidelines

Hilt itself does not affect store guidelines directly. However, ensure your app complies with Google Play policies on performance and security. Avoid injecting sensitive data directly; use secure storage. Also, keep your app responsive and avoid long startup delays caused by heavy dependency initialization.

Self-Check Question

Your app takes 5 seconds to load this screen. What's likely wrong?

• Heavy dependencies are created eagerly on the main thread instead of lazily.
• Incorrect scoping causes multiple instances, increasing memory and startup time.
• Annotation processing or generated code is not optimized or ProGuard/R8 is disabled.

Key Result

Using Hilt improves app startup and memory efficiency by managing dependencies smartly. Optimize injection scopes and lazy loading to maintain smooth 60fps UI. Enable code shrinking to keep app size small. Remember, Hilt is Android-specific and requires proper setup for best performance and store compliance.

Practice

1. What is the primary purpose of using @HiltAndroidApp annotation in an Android application?

easy

A. To inject dependencies into a ViewModel

B. To mark an Activity as injectable by Hilt

C. To trigger Hilt's code generation and setup the application-level dependency container

D. To define a module that provides dependencies

Solution

1. Step 1: Understand the role of @HiltAndroidApp

   This annotation is placed on the Application class to start Hilt's code generation and create the application-level dependency container.

2. Step 2: Differentiate from other annotations

   @AndroidEntryPoint marks Activities or Fragments, @Module defines providers, and @Inject is for injection points, so they do not setup the application container.

3. Final Answer:

   To trigger Hilt's code generation and setup the application-level dependency container -> Option C

4. Quick Check:

   @HiltAndroidApp = Setup app container [OK]

Hint: Remember: @HiltAndroidApp is only on Application class [OK]

Common Mistakes:

• Confusing @HiltAndroidApp with @AndroidEntryPoint
• Thinking @HiltAndroidApp is for Activities
• Using @HiltAndroidApp on modules

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 lateinit var for the dependency

B. Use @Module annotation on the Activity and call inject() manually

C. Add @HiltAndroidApp on the Activity and initialize dependencies in onCreate()

D. Declare dependencies as constructor parameters without annotations

Solution

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

   Using @AndroidEntryPoint on the Activity allows Hilt to generate necessary code for injection.

2. Step 2: Inject dependencies inside Activity

   Use @Inject lateinit var to declare dependencies that Hilt will provide automatically.

3. Final Answer:

   Annotate the Activity with @AndroidEntryPoint and use @Inject lateinit var for the dependency -> Option A

4. Quick Check:

   @AndroidEntryPoint + @Inject lateinit var = Activity injection [OK]

Hint: Use @AndroidEntryPoint on Activity and @Inject lateinit var inside [OK]

Common Mistakes:

• Trying to use @Module on Activity
• Forgetting @AndroidEntryPoint annotation
• Injecting dependencies via constructor in Activity

3. Given the following Hilt module code, what will be the output when repository.getData() is called?

@Module
@InstallIn(SingletonComponent::class)
object DataModule {
    @Provides
    fun provideData(): String = "Hello Hilt"
}

class Repository @Inject constructor(private val data: String) {
    fun getData() = data
}

medium

A. "DataModule"

B. Compilation error due to missing @Inject on Repository

C. NullPointerException at runtime

D. "Hello Hilt"

Solution

1. Step 1: Understand the provided dependency

   The module provides a String "Hello Hilt" via the provideData() function.

2. Step 2: Check Repository injection

   Repository constructor is annotated with @Inject and receives the String dependency correctly.

3. Final Answer:

   "Hello Hilt" -> Option D

4. Quick Check:

   Provided String = "Hello Hilt" [OK]

Hint: Look for @Provides return value matching injected type [OK]

Common Mistakes:

• Assuming @Inject missing on Repository causes error (it is present)
• Confusing module name with provided value
• Expecting runtime null error without reason

4. Identify the error in the following Hilt setup:

@Module
@InstallIn(ActivityComponent::class)
object NetworkModule {
    @Provides
    fun provideRetrofit(): Retrofit {
        return Retrofit.Builder().baseUrl("https://api.example.com").build()
    }
}

@AndroidEntryPoint
class MainActivity : AppCompatActivity() {
    @Inject lateinit var retrofit: Retrofit

    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
    }
}

medium

A. Retrofit cannot be provided in ActivityComponent scope because it should be Singleton

B. Missing @Inject constructor in Retrofit class

C. MainActivity must be annotated with @HiltAndroidApp

D. Retrofit instance must be created manually, not with @Provides

Solution

1. Step 1: Check the component scope for Retrofit

   Retrofit is usually a singleton because it is expensive to create and shared across app.

2. Step 2: Analyze the module's @InstallIn scope

   The module is installed in ActivityComponent, which creates a new instance per Activity, not singleton.

3. Step 3: Identify the mismatch

   Providing Retrofit in ActivityComponent scope causes multiple instances, which is incorrect for Retrofit.

4. Final Answer:

   Retrofit cannot be provided in ActivityComponent scope because it should be Singleton -> Option A

5. Quick Check:

   Retrofit = Singleton scope needed [OK]

Hint: Provide expensive objects in SingletonComponent scope [OK]

Common Mistakes:

• Thinking Retrofit needs @Inject constructor
• Confusing @HiltAndroidApp with @AndroidEntryPoint
• Believing manual creation is required with @Provides

5. You want to inject two different implementations of an interface Logger using Hilt in your Android app. Which approach correctly distinguishes these implementations for injection?

hard

A. Provide both implementations in the same module without qualifiers and inject List<Logger>

B. Use @Qualifier annotations with different names on each provider and injection site

C. Use @Singleton on both implementations and inject Logger directly

D. Create separate modules for each implementation without any annotations

Solution

1. Step 1: Understand multiple implementations injection

   When multiple implementations of the same interface exist, Hilt needs a way to distinguish them.

2. Step 2: Use @Qualifier annotations

   Custom @Qualifier annotations with different names allow Hilt to know which implementation to inject where.

3. Step 3: Reject other options

   Injecting List<Logger> is possible but does not distinguish single injection points; @Singleton does not differentiate implementations; separate modules without qualifiers cause ambiguity.

4. Final Answer:

   Use @Qualifier annotations with different names on each provider and injection site -> Option B

5. Quick Check:

   Multiple implementations = use @Qualifier [OK]

Hint: Use @Qualifier to name different implementations [OK]

Common Mistakes:

• Injecting interface without qualifiers causes errors
• Assuming @Singleton differentiates implementations
• Not using qualifiers when multiple providers exist