Performance for Android Developers
Android performance is how smoothly and efficiently an app runs: fast startup, frames drawn without jank, low memory use and modest battery drain. You measure it with Android Studio Profiler, Macrobenchmark and Perfetto, then fix causes such as work on the main thread, leaks and unnecessary recomposition.
Stage: Quality and Performance · Part of the Android Developer roadmap · Last reviewed 19 November 2026
What to learn in Performance
- Record a CPU trace and find the function blocking the main thread
- Detect a memory leak with the heap profiler and LeakCanary
- Measure cold startup time with a Macrobenchmark
- Reduce overdraw and unnecessary recompositions in a slow screen
- Choose battery-friendly scheduling for background work
Performance interview questions
What causes jank in an Android app?
Jank appears when a frame takes longer than the display budget, about 16 ms at 60 Hz, so frames are skipped. Typical causes are heavy work on the main thread, large layout or composition passes, big image decoding, and garbage collection pauses from excessive allocation.
How do you find a memory leak in Android?
Capture a heap dump in the Memory Profiler after navigating away from a screen and look for Activity or Fragment instances that should be gone. LeakCanary automates this and shows the reference chain. Common causes are static references, unregistered listeners and long-lived coroutines holding a context.
Where Performance fits in the Android Developer roadmap
Performance belongs to the Quality and Performance stage (beginner level), which takes about 5 hours. Reliable and fast.
Other units in this stage
Back to the full Android Developer roadmap