r8-analyzer

Android app size reduction is achieved by analyzing R8 keep rules to identify redundant, overly broad, or harmful configurations. This skill evaluates project-specific ProGuard files and Gradle settings to generate actionable recommendations for pruning high-impact rules and shrinking the APK.

R8 blast radius data calculates precise optimization, shrinking, and obfuscation scores by analyzing internal build configurations. It identifies exactly how modifying specific keep rules impacts overall app size and code obfuscation, enabling data-driven optimization decisions.

For older Android projects lacking quantitative data, heuristic recommendations identify redundant library rules and optimization opportunities. It evaluates existing build configurations to provide actionable advice on safely removing unnecessary ProGuard rules without causing runtime crashes.

Yes, analyzing R8 configuration requires access to project build files and the ability to execute Gradle tasks. This access is necessary to evaluate project-specific ProGuard files and Gradle settings for optimization opportunities accurately.

Removing ProGuard keep rules causes runtime crashes when configurations are overly broad or incorrectly pruned, stripping necessary class references. R8 analysis identifies which rules are truly redundant versus which are essential for preventing crashes while reducing app size.