Diagnose Android UI jank using Android Studio's Profiler

WHAT THIS TESTS: This question tests whether you can move from a vague user complaint to an actionable engineering diagnosis using Android Studio Profiler. The interviewer wants to see methodical debugging: choosing the right profiler, knowing the 16ms frame budget on a 60Hz screen, distinguishing CPU-bound work from memory pressure, and avoiding guesswork.

A GOOD ANSWER COVERS: First, state you would start with the CPU Profiler and record a system trace while reproducing the jank. Second, explain you would look at the Frame Timeline or Frames track to spot frames exceeding 16ms. Third, drill into the main thread to find long-running methods, blocking I/O, or excessive layout passes. Fourth, mention cross-checking the Memory Profiler for garbage collection spikes or memory churn that causes stutter. Fifth, note you would inspect thread states like sleeping or blocked to see if the issue is contention rather than computation.

COMMON WRONG ANSWERS: A red flag is jumping straight to Logcat or blaming the user's low-end device without profiling. Another mistake is mentioning only high-level fixes like optimize layouts or use RecyclerView without first identifying the bottleneck via a trace. Saying you would use the Network Profiler as the first step for UI jank is also off-target unless the freeze is clearly tied to a network callback.

LIKELY FOLLOW-UPS: The interviewer may ask how you would fix a specific long-running method on the main thread, how Systrace differs from the built-in CPU Profiler, or what you would do if the trace shows no main thread work but frames still drop. They might also ask about the impact of a 90Hz or 120Hz display on the frame budget, or how to automate jank detection in CI.

ONE CONCRETE EXAMPLE: Suppose a user scrolls a list and the app freezes. You record a CPU trace and see the Frame Timeline shows a 42ms frame. On the main thread, you find a JSON parsing loop running inside onBindViewHolder. You move that work to a background thread with coroutines, re-run the trace, and verify all subsequent frames drop back under 16ms. You also check the Memory Profiler and notice a GC spike every scroll; you fix it by reusing view holders and reducing object allocations, which smooths the scroll further.