Android ANR reports arrive with volume and little narrative. During release health work we treat them as clusters, not as individual stack frames.
Start with user-visible hangs
Prioritize clusters that coincide with first-session journeys: login, home feed, checkout start. A hang deep in a background sync may be real, but it rarely decides a staged expand the same night.
Device class matters more than raw count
Mid-range devices with older OS builds often dominate ANR volume. If your expand plan was already limited to newer devices, an ANR spike on unsupported hardware should inform messaging — not necessarily a full hold.
Tie ANRs to the change list
Map each top cluster to a plausible change from the release notes: new splash logic, a tightened timeout, a WebView update. If nothing maps, say so. Unknown clusters deserve a monitor recommendation, not false confidence.