Wanna get rid of UI Jank?
summary
Sample app rendering shows 270 frames with 177 dropped, traced with dumpsys gfxinfo and visualized with Profile GPU Rendering so the problem is bitmap work during bind; system-level systrace surfaces 57 bitmap-upload alerts and per-frame red bars over 16 ms, and adding Glide caching removes the jank. Also uses Android CPU profiler, recommends >10% dropped frames as a failure, avoid nested layouts, use DiffUtil, and inspect GPU overdraw colors to prioritize fixes.
AI-written summary · about
chapters (13)
- 0:00Introduction to UI Jank
- 1:34Why UI performance matters
- 3:39Causes of UI Jank issues
- 5:49Demo of UI jank in sample app
- 7:12Using Dumpsys to detect jank
- 8:15Profile GPU rendering tool
- 10:25Analyzing traces with systrace
- 13:40Fixing bitmap loading issues
- 15:29Best practices for UI performance
- 17:18Overdraw and its impact
- 19:04Focus on major performance issues
- 19:49Android Vitals and fragmentation
- 20:30Collaborating with designers
related talks
28mOptimizing and Profiling UI Performance
43mNo More Jank: Escaping the Matrix of Frame Drops
37mUI profiling in examples. Where is my bottleneck?
44mNo More Jank: How to Keep Your Flutter App Smooth and Snappy
53mGraphics Something Android Something Performance
47mG(PU) force
21mThe UI Was Beautiful. The Frame Rate Wasn’t. Why We Didn’t Fix It.
07mDebugging RN Android Performance