r8-analyzer

To find redundant R8 keep rules, you need an analysis tool that inspects your Android Gradle build configuration and Proguard keep rules to detect overly broad patterns preventing code shrinking. The r8-analyzer Skill evaluates these rules and generates a structured Markdown report highlighting optimization opportunities.

The best way to check if Proguard keep rules limit shrinking and obfuscation is to run a quantitative or heuristic analysis on your R8 configuration. Depending on your R8 version, the analyzer generates configuration datasets or reviews broad rule patterns to identify wasteful keep rules.

Yes, R8 full mode requires different keep rule analysis because its optimization settings and expectations differ from older Proguard setups. The analysis verifies your Android Gradle configuration alignment and chooses between quantitative dataset generation or heuristic fallback inspection based on the detected R8 version.

To analyze R8 configuration analyzer output, you parse the generated dataset to derive optimization impact metrics for your keep rules. When quantitative analysis is unsupported, you evaluate rules using heuristic fallback inspection and rule hierarchy guidance to prioritize refinements.

Android release builds may not shrink because overly broad R8 keep rules protect unnecessary classes from removal. Inspecting your build.gradle and gradle.properties files reveals misaligned app-optimization settings or redundant rules that limit obfuscation and increase app size.

After refining R8 keep rules, you should validate proposed changes using macrobenchmark-style testing with UI Automator to reduce regression risk. This release-safety focus ensures that removing redundant keep rules does not break app functionality during obfuscation and shrinking.