Google Play Says “App Optimisation Is Below Our Threshold”: What 0% Obfuscation Means

What does 0% obfuscation mean?

Obfuscation shortens names of classes, methods, and fields in compiled code. It is one part of code optimisation, alongside shrinking and other transformations. A 0% reading means Google Play detected little or no obfuscation for this release. It does not, by itself, prove that the app has a memory leak or is behaving badly.

Google explains that DEX code optimisation can reduce code size, improve runtime performance, and lower memory use. Play Console calculates its percentage using build metadata when available, a mapping file, or DEX analysis, depending on the build. Read Google’s DEX code optimisation guidance.

How to investigate release 8 (8.0)

1. Confirm the affected artifact. In Play Console, identify the app bundle and track for release 8 (8.0). Record the exact deadline and any other optimisation percentages shown.
2. Check the release build configuration. For an Android Gradle Plugin build using the legacy DSL, ensure the release variant enables R8 code minification (minifyEnabled = true in Groovy or isMinifyEnabled = true in Kotlin). Follow the configuration appropriate to your plugin version. Google’s R8 setup guide includes current and legacy examples.
3. Review keep rules. Broad rules can preserve entire packages and prevent obfuscation. Narrow them only after checking which classes genuinely need their original names, such as code accessed through reflection or serialization.
4. Build and test a new release. Exercise startup, sign-in, navigation, background work, and any reflection-heavy or third-party SDK features. Keep the mapping file so obfuscated crash traces can be decoded.
5. Upload the corrected bundle and recheck Play Console. Verify the new optimisation percentage for the new artifact rather than assuming a successful build resolves the warning.

What about “Memory usage” and “Bad behaviour”?

Those labels are useful reminders to inspect Android vitals, but the 0% figure in this notice is for obfuscation. R8 optimisation may reduce memory pressure and improve performance, yet memory usage and user-visible failures still need their own measurements and fixes. Review crashes, ANRs, and memory data separately after publishing the corrected release.

The takeaway

Treat the warning as an actionable build-quality issue for release 8 (8.0): confirm the deadline, enable appropriate release optimisation, refine overly broad keep rules, test the result, and verify the updated percentage in Play Console. The exact fix depends on the app’s build system and current configuration.