Android Multidex: When You Need It and When You Do Not

Understand the platform split

Android 5.0 and later provide native support for loading multiple DEX files. Applications that support earlier platform versions need the appropriate AndroidX multidex support path. Your minSdk therefore determines whether legacy initialization is relevant. Android multidex guide.

The limit concerns method references in a DEX file, not the number of source-code methods you personally wrote. Dependencies and their transitive libraries contribute too. DEX structure.

Reduce unnecessary code before adding complexity

Inspect the resolved dependency tree for unused or duplicated libraries. Enable release shrinking where appropriate and avoid broad keep rules that preserve entire SDKs unnecessarily. Multidex makes a large codebase packageable; it does not remove the cost of code that should never have been included.

Check the release variant separately from debug. Test libraries and debugging integrations may distort a debug-only diagnosis.

Configure legacy support only when required

For an application that genuinely supports pre-21 Android, the relevant build setting is:

android {
    defaultConfig {
        multiDexEnabled = true
    }
}

The AndroidX multidex dependency and application initialization must also be configured as documented. This fragment alone is not a complete legacy setup. For minSdk 21 or higher, do not add legacy initialization solely because multiple DEX files appear in the APK.

Inspect the produced files

Use:

apkanalyzer dex list app-release.apk

Expecting only classes.dex after enabling multidex is a mistaken success criterion. The important checks are whether the build succeeds, the required classes are packaged and the app starts correctly on the oldest supported platform.

Diagnose startup failures separately

On legacy platforms, initialization-time classes may need to be available before secondary DEX loading. Reflection and unusual application startup paths can complicate detection. Read the earliest ClassNotFoundException or related stack instead of repeatedly increasing heap settings or deleting caches.

APKLint's DEX analyzer can help inventory the package. It does not run Android's class loader or prove that a legacy startup path works. Test the actual minimum-supported device configuration before shipping a multidex change.