Optimize your app performance for the next generation of Android
summary
Android 17 enforces process memory budgets via cgroups while Play Console adds a rolling-out memory section with P99 vs P50 and RAM-bucket histograms; Profiling Manager (integrated with Datadog and coming to Crashlytics) captures cold-start, CPU-kill, OOM and anomaly traces. R8 plus the R8 configuration analyzer reports shrinking, optimization and obfuscation scores; Monzo sees ANR −35%, cold start −30% and app size −9% after full R8. Bitmap rules: request server-sized assets, prefer hardware bitmaps or RGB_565 for thumbnails, use vectors, and use startup/baseline profiles and ActivityManager exit reasons to recover state.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:58Memory on Android
- 9:16App memory limits in Android 17
- 10:12In-field monitoring and profiling
- 15:24R8 and memory optimization
- 20:34Bitmaps and image management
- 27:48App resilience and Low memory killer daemon
- 30:24Track app kills and handle memory pressure
- 33:47Recap of app optimization techniques
- 35:06Improve startup time with profiles
- 36:06Save UI state with rememberSaveable
- 37:12Session summary
related talks
38mOptimize your app performance for the next generation of Android
38mLow effort, High impact Android performance wins
01h 06mOptimize your apps for Android (Go edition)
40mAndroid vitals: Debug app performance and reap rewards
36mAndroid memory and games
46mDeveloping for Android: the Naughty Bits
45mHigh performance in Android
41mWays to reduce your app’s memory and storage footprint