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.
This article details Android .so compression and remote loading techniques, covering compile‑time selection, custom Gradle tasks, runtime loading logic, size‑reduction results, bandwidth considerations, and practical flow‑control configurations to balance performance and user experience.
This article examines the problem of growing APK sizes caused by R.java files in JD.com's Android pluginized client, analyzes the feasibility of R file slimming, and presents a Gradle Transform and ASM‑based solution that inlines resource IDs, removes R files, and achieves 3‑5% size reduction without noticeable build‑time impact.
This article reviews Youku's five‑year journey of Android APK size reduction, detailing the shift from special‑project squeezes to sustainable normal governance, the technical measures and analysis tools like Franky, and practical slimming techniques that can help any mobile team manage package size efficiently.
Over five years, Youku’s Android team systematically reduced APK size through specialized and continuous governance, employing remote modules, whole‑package optimizations, and precise analysis tools like Franky, ultimately cutting the app from over 120 MB to under 65 MB while maintaining performance and stability.
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.
