Android Code Obfuscation: ProGuard vs R8 and Configuration Guide

Code obfuscation is an essential step for Android developers when building release APKs, typically enabled by setting minifyEnabled true . The article explains the underlying principles, the evolution of obfuscation compilers (ProGuard and its successor R8), and how they integrate with the Android Gradle Plugin.

It outlines the timeline of ProGuard and R8 support across AGP versions, showing when each became default. The four core functions—shrink (compress), optimize, obfuscate, and preverify—are described, with differences between ProGuard and R8 highlighted.

Configuration examples demonstrate how to explicitly enable or disable R8/D8, control minifyEnabled , shrinkResources , and specify ProGuard rule files. Sample build.gradle snippets illustrate settings for preview, release, and debug build types.

The article details ProGuard rule syntax, common directives such as -keep , -dontshrink , -dontoptimize , and how annotations like @Keep affect rule generation. It also explains the three sources of rule files: Android Gradle plugin, AAPT2, and module‑specific files.

For modular projects, the impact of module‑level obfuscation is examined. Tests show that only the App module’s ProGuard rules are applied to the final APK, while library module rules require consumerProguardFiles to be merged. Componentized obfuscation strategies and their trade‑offs are discussed.

In summary, ProGuard is a general Java bytecode optimizer, whereas R8 is Android‑specific and combines shrinking, optimization, obfuscation, desugaring, and DEX conversion into a single step, offering better build performance and smaller artifacts.