Field note

ANR notes product leads can actually use

2026-01-08 · Arthit Phongphairote

Application Not Responding reports need translation. Here is how we turn freeze stacks into decisions non-engineers can act on.

Product leads rarely need raw stack traces. They need to know which screen froze, how often, and whether the freeze blocks revenue or trust. Our monthly briefs open with that framing before any technical detail.

Group ANRs by user-visible moment: home feed load, camera capture, payment sheet. That grouping reveals whether the problem is a single feature or a broader main-thread habit across the app.

Ask engineering for one sentence on thread ownership when a freeze signature repeats. Ownership clarity shortens the path from report to assignee without turning the product meeting into a debugging session.

When freeze rates rise only on older devices common in your market, record that constraint. A Thailand-facing release often serves a wider device age range than a pilot among flagship phones.

Treat a single dramatic ANR clip as a prompt to investigate, not as proof of scale. Volume and uniqueness still decide whether you delay a release.

Back to field notes · Request a stability review