Ways to reduce your app’s memory and storage footprint
summary
Practical signals and fixes decide whether to watch: use Google Play Console LMK rates and the ApplicationExitInfo LMK reason API to prove low-memory kills, run Android Studio memory profiler and heap dumps plus LeakCanary in Android Studio to find duplicate bitmaps, and measure savings from modern formats like AVIF 270 KB vs JPEG 1.2 MB. Replace WebViews for simple content (image rendering can double memory), switch to RGB_565 or hardware bitmaps, use bitmap pools, enable R8 shrinking, and implement onTrimMemory and autoCloseable to verify real, repeatable gains.
AI-written summary · about
chapters (14)
- 0:00Memory and storage optimization
- 1:05Memory usage impact
- 5:46Identifying memory issues
- 10:20Profiling memory usage
- 13:31Optimizing bitmap images
- 17:50Modern image formats
- 20:18Vector drawables and fonts
- 23:32R8 and code optimization
- 25:18Library and overhead costs
- 27:02WebView and JSON overhead
- 28:06Memory management
- 34:23Auto-closeable and cleanup
- 35:24Storage management
- 36:48Memory optimization summary
related talks
23mReducing memory footprint of your app - what LeakCanary is not telling you about
38mOptimize your app performance for the next generation of Android
22mHow to Make Your App Lose Weight
29m10 Ways To Improve Your Android App Performance- 38mOptimize your app performance for the next generation of Android
33mPruning Your App- Good Practices for Reducing App Size
40m640K ought to be enough for anyone
25mMemory leaks on Android: lessons learned and methodology