This article explains the differences between D8 and R8, details R8’s advanced optimization techniques, discusses challenges like reflection and keep‑rules, and highlights recent tooling improvements and future features that make R8 essential for faster, smaller Android apps.
This guide explains why Android performance matters to users, developers, and business, then walks through Google’s diagnostic tools, R8 optimization steps, continuous monitoring, and a Reddit case study that turned a two‑week effort into a one‑star rating boost.
This article explains how R8’s ApiModel optimization can generate a redundant new‑instance bytecode that triggers class initialization failures, why synchronized or try‑catch blocks also cause the issue, and presents four practical solutions including disabling ApiModel, official patches, custom fixes, and business‑level refactoring.
A mobile app deadlock was traced to a do‑while loop introduced by a weaver plugin that concurrently copied method nodes, causing ASM label‑node mismatches; adding thread synchronization to the method‑cloning process resolved the issue and underscores the concurrency risks of bytecode instrumentation.
The article explains how a missing keep rule caused R8’s pre‑AGP 8 reflection optimizer to skip a class because its interface wasn’t in the allowed set, leading to the class name being obfuscated and mismatched in static‑block initialization via Class.forName, and describes the optimizer’s behavior and fixes.
After upgrading Kuaishou's Android project from AGP 3.4.2 to 7.0.1, the APK size unexpectedly grew despite faster builds, leading to a deep investigation of Dex compression, R8 changes, and build tool versions, ultimately revealing a fastutil library mismatch that was resolved by forcing the correct version.
The article explains how Meituan migrated its method‑instrumentation hot‑fix system Robust from ProGuard to Google’s R8 by moving change detection ahead of optimization, disabling or tuning R8’s built‑in optimizations, and implementing special handling for anonymous classes, inlined methods, super calls, constructors and static initializers to ensure reliable patch generation.
This article explains how WeChat Android moved from Proguard to R8, detailing the performance and size gains, the new build workflow, the numerous optimization pitfalls encountered, and the concrete fixes applied to ensure stable releases and smaller Tinker patches.
This article details JD's Android app package‑size reduction journey, covering component analysis with APK Analyzer and zipinfo, dependency mapping via Gradle, a suite of slimming measures such as plugin‑to‑download, resource compression, R8, 7‑zip, and a systematic governance framework that ties component growth to enforceable size‑control policies, ultimately achieving over 30% reduction in APK size.
The article explains why reducing APK size improves download conversion and performance, then details a systematic, divide‑and‑conquer approach for Baidu App that trims Dex, resources, native libraries and ZIP overhead using tools such as R8, AndResGuard, ByteX, Booster and AGP, achieving a reduction from roughly 123 MB to 115 MB with up to 6 MB saved per batch and outlining plans to open‑source the utilities.
This article details JD's Android app migration to the R8 compiler, explains differences between ProGuard and R8, analyzes the impact of the -useuniqueclassmembernames rule, addresses v1 signing loss after AGP 3.6.4 upgrade, and provides practical solutions for build‑process ordering and packaging pitfalls.
The Baidu App team applied a systematic, sustainable approach—combining Dex, resource, and native‑library optimizations with tools such as R8, ProGuard, AndResGuard, and custom compression pipelines—to shrink the APK by several megabytes, improve download conversion, and establish reusable mechanisms for future builds.
This article explains the hidden problem of engineering decay in Android app development, introduces Proguard/R8 core functions, details global and keep configurations, showcases detection tools and governance practices, and provides actionable steps to reduce build time and APK size.
Upgrading from AGP 3.5.0 to 4.1.0 dramatically simplifies R class generation, removes redundant R files via R8‑based inlining, reduces APK size by ~7 MB, and speeds up release builds by over ten minutes, as demonstrated through detailed build‑artifact comparisons and Gradle task analysis.
This article provides a comprehensive guide to Android code obfuscation, covering the purpose and benefits of minification, detailed ProGuard/R8 configuration, resource shrinking, desugaring, D8/R8 internals, custom obfuscation dictionaries, and modular ProGuard rules for multi‑module projects.
