‘Application Not Responding’ is a state in which the app is frozen and does not respond to any user input. This can have a direct effect on conversion rates, retention rates, and overall user experience. Unlike unresponsive gestures which are attributed to a design decision (e.g. an image that mistakenly looks like a tappable button), ANRs usually occur due to long running code that freezes the “UI thread”.
Appsee detects app freezes that last more than 5 seconds and shows these both on an individual session level and within screen-level aggregated reports. Accordingly, we have also enriched our ‘Crashes’ section so that it is now entitled ‘Issues’ and contains both crashes and ANRs. Now you can quickly and clearly identify which screens have ANR issues, manage their status (resolved/closed), and add comments for team members, just as you could with crash issues.
While Google Play Developer Console can also track ANR states, Appsee is the only mobile app analytics platform in the industry that is able to provide ANR data along with visual user session insights. Appsee’s ANR tracking is available for both iOS and Android apps (2.3.3 for Android, 2.3.5 for iOS).
What is the difference between ANR, “App Kill” and Unresponsive Gestures?
Unresponsive Gesture – Appsee’s SDK tracks all gestures (pinches, swipes, taps etc.) which may not be recognized by your application. These are attributed to a design decision (e.g. an image that mistakenly looks like a tappable button),
ANR – Application Not Responding is a state that exists where the app is stuck in a process and does not respond to user input. Technically, this happens when the app’s UI thread is frozen for more than 5 seconds.
App Kill – An app is considered killed when the user ends it in an ungraceful manner, through the task manager. When users encounter an ANR, the app is frozen, and usually, they will kill the app because they have no other option.