Dynamic Feature Module with Hilt

Android — Clean architecture with Dynamic-features and Hilt/Dagger2 (Pt.1)

Setting up Gradle files!

https://pedrookawa.medium.com/clean-architecture-with-dynamic-features-and-hilt-dagger2-pt-1-d1be41a44b12

Hilt in multi-module apps  |  App architecture  |  Android Developers

Hilt code generation needs access to all the Gradle modules that use Hilt. The Gradle module that compiles your Application class needs to have all Hilt modules and constructor-injected classes in its transitive dependencies.

https://developer.android.com/training/dependency-injection/hilt-multi-module

Dynamic feature module with Hilt

I try to make my feature module as a dynamic feature module while I am using Hilt as dependency injection framework. I receive following exception : caused by: java.lang.ClassCastException: com.and...

https://stackoverflow.com/questions/68444389/dynamic-feature-module-with-hilt

✅ Why your Dynamic Feature Module looks like it is “embedded” in the APK

👉 Dynamic Feature Modules work ONLY with App Bundles (.aab), NOT with standalone APKs.

• APK (app-release.apk) → Everything is merged into one file → dynamic module looks “embedded”

• App Bundle (app-release.aab) → Dynamic features become truly dynamic (separate, on-demand installable)

🧩 So what actually makes a module “dynamic”?

1. You apply this plugin:

plugins {
    id("com.android.dynamic-feature")
}

2. You add it to base module:

dynamicFeatures = [":feature_player"]

3. You build an App Bundle:

Build > Build Bundle(s) / APK(s) > Build Bundle(s)

4. Play Store or Play Core delivers the feature module on demand, for example:

splitInstallManager.startInstall(
    SplitInstallRequest.newBuilder()
        .addModule("feature_player")
        .build()
)

🔥 IMPORTANT → APK vs AAB Behavior

When building APK

When building AAB

⭐ TL;DR

✔ Your confusion resolved

→ Build an App Bundle (.aab)

→ Upload to Play Store or test with bundletool

You said:

ChatGPT said:

✅ Step-by-Step: Test Dynamic Feature Module locally

STEP 1 — Build an App Bundle (.aab)

Build > Build Bundle(s) / APK(s) > Build Bundle(s)

app-release.aab

STEP 2 — Install bundletool

bundletool.jar

STEP 3 — Generate a local “fake Play Store” set of APKs

java -jar bundletool.jar build-apks \
  --bundle=app-release.aab \
  --output=app.apks \
  --mode=universal

java -jar bundletool.jar build-apks \
  --bundle=app-release.aab \
  --output=app.apks \
  --connected-device

• Base apk

• Feature module apk(s)

• Config apks

STEP 4 — Install it as Play Store would do

java -jar bundletool.jar install-apks --apks=app.apks

STEP 5 — Trigger your dynamic module download from the app

val manager = SplitInstallManagerFactory.create(context)

val request = SplitInstallRequest.newBuilder()
    .addModule("feature_player")   // your module name
    .build()

manager.startInstall(request)
    .addOnSuccessListener {
        Log.d("DFM", "Module download started")
    }.addOnFailureListener {
        Log.e("DFM", "Install failed: $it")
    }

🎉 STEP 6 — Watch the feature module download LIVE

Downloading module: feature_player
Install success

• Feature is delivered as a separate APK

• Your Activity/Fragment from that module now becomes available

• App size increases dynamically

⭐ OPTIONAL — Verify installed modules

adb shell pm list packages -f

.../split_feature_player.apk=your.package.name

🧪 BONUS — Force uninstall dynamic module to test again

adb shell pm uninstall your.package.name

✔ TL;DR (Fast Summary)