Improving App Upgrade Rates & Reducing APK Size
summary
At scale, upgrade gaps leave whole regions stuck on old clients so test upgrade paths beyond x+2 (some teams hit 120 versions or x+30), measure regional uptake, and set a deprecation window months ahead. Shrink APKs by enabling Redex and D8 in Gradle, use image compression like Zopley, compress native libs at build time, split by density/ABI and serve large features via APK splits or dynamic delivery, and download bulky assets on demand to raise auto‑update success.
AI-written summary · about
chapters (7)
- 0:00Introduction to upgrade challenges
- 3:17Why upgrades fail in emerging markets
- 6:52Making upgrades easier and more appealing
- 9:19Pitfalls in long-term upgrade paths
- 11:50Reducing APK size effectively
- 18:54Optimizing assets and features
- 20:19Key takeaways and Q&A
related talks
19mA journey to smaller apk size
22mHow to Make Your App Lose Weight
40mGenerating efficient apk by reducing size
33mPruning Your App- Good Practices for Reducing App Size
29m10 Ways To Improve Your Android App Performance
41mShrink, Secure & Optimize Your App With R8
33mOptimization - Making your app faster
40mAttributed Everything: Ensuring Quality for Large Apps