UI profiling in examples. Where is my bottleneck?
summary
App rendering misses the 16 ms budget (60 fps), so use GPU rendering bars, Hierarchy Viewer / Layout Inspector and Android Studio CPU profiler to find whether time is spent in waiting (dark green/orange), layout/measure, or draw. Concrete fixes shown: heavy EditText instances and redundant container fragments create ~300 views and produce 13–40 ms spikes; overlapping backgrounds cause overdraw; nested RecyclerView/ScrollViews force full measurement. Use Android Vitals and Firebase Performance Monitoring to collect traces from real devices and verify fixes.
AI-written summary · about
chapters (11)
- 0:00Start
- 12:49Aggregated data
- 18:48ViewStub vs Dynamic
- 21:05Test on slower devices
- 21:29Know you tools
- 23:03Hierarchy Viewer - thread time
- 23:39Hierarchy Viewer. Conclusion
- 24:59Debug GPU overdraw
- 33:59Frozen Frames
- 34:11Render time anomaly
- 35:01Firebase Performance Monitor
related talks
33mUI profiling in examples. Where is my bottleneck?
45mFinding and Fixing Performance Problems
45mHigh performance in Android
46mProfiling with Examples: Hunting the Bottleneck
07mDebugging RN Android Performance
28mOptimizing and Profiling UI Performance
21mWanna get rid of UI Jank?
34mPerformance in a Kotlin world