Advanced Android app shrinking techniques
summary
Compares concrete builds of the FODM companion app and Tusky, using Android Studio APK Analyzer, Gradle dependency trees and R8 to measure effects: switching to the program Android optimize rules cuts dex size by about 33% in FODM (25% in Tusky) with an extra ~5% (150 KB ~3% in Tusky) from custom rules; converting map PNGs to lossless WebP yields ~20% smaller images; removing unused locales saves ~200 KB; assertions removal trims ~2% of dex.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:30Smaller app packages matter
- 2:55APK structure basics
- 3:58Optimizing images with WEBP
- 7:11Removing unsupported locales
- 8:58Cleaning metadata and native binaries
- 10:45Optimizing dependencies
- 13:54Advanced R8 rules
- 19:10Removing Kotlin assertions
- 21:20Debugging rules and libraries
- 24:52XML resources and unreachable code
- 32:42Migrating to Jetpack Compose
- 35:29Compose results and plans
- 36:10Q&A
related talks
22mHow to Make Your App Lose Weight
41mShrink, Secure & Optimize Your App With R8
41mShrinking Your APK, By Example
29m10 Ways To Improve Your Android App Performance
34mOptimize your app size with this one trick
28mEscaping from a 'It Kinda Works' ProGuard Setup
38mLow effort, High impact Android performance wins
38mOptimize your app performance for the next generation of Android