Scene of the Crash: Seeing Crash Statistics for Individual Users

When you find out that your app is crashing for some of your users, you know it’s time to start digging through data to figure out what’s wrong, and what you need to do to correct it.

Where to start? We believe the best approach is to begin the debugging process by looking at aggregate performance levels of your app on different devices, to get a sense of how well the app is performing overall, and then drilling down to individual user’s experiences until you find the answer. Embrace lets you do both easily.


Right away we can look at what percent of your users are using which device, and of those, what percent of them are crashing. If one or more devices is crashing above what its baseline percentage of users is, this tells you that you have issues that need to be addressed over and above any individual crashes. You now have a head start on what work you might need to do.


App performance monitoring
Let’s use Out Of Memory exception errors as an example, although we would do the same thing for other types of crashes. In our example, we can see that the iPhone 6 Plus and iPad Air 2 are causing OOM errors way beyond what they should, based on their number of app users. The same is true for iOS 11.2.1 and 11.4. What common features do these devices and OS versions have that may lead to the problem? You’ve got someplace to start.

Next, we start looking at individual crashes. Now you see where the Embrace approach to app performance monitoring makes your job much easier. When you drill down deeper, you can see each crash sorted by the last screen the user viewed, which lets you focus on a possible cause for the issue.


App performance monitoring
Clicking on any of the crashes lets us look at the relevant information about the context of the crash, so we can try to figure out the cause.


App performance monitoring
Looking more closely, we can see exactly what the user was doing from the time they launched your app until the OOM error appeared. That includes the time they spent elsewhere while your app was in the background. Every event, such as a network call or adding an item to a shopping cart, is available to examine. You can see where they tapped on the screen, and view a screenshot of what they were looking at. You also get a complete profile of the user’s device, including how much of their hard memory was used.

You don’t need a phone call to the user to ask all the usual questions, because we provide that info for every user, and every session. If your app provides user IDs to your user, we’ll show you all sessions by that user. We provide a complete set of error logs, each of which allows you to look not only at all the errors generated, but drill down into each error to see all of the information we’ve gathered, and also see other errors that the same user has experienced.

No one else provides this level of visibility into your app’s user activities. It’s the kind of information that helps you get to the bottom of problems as quickly and efficiently as possible. Interested in seeing Embrace in action? Take it for a test drive today!

If you found a few bits of value, please share:
Improving Your Conversion Funnel in 4 Steps
Lowest Hanging Fruit for Improving App Performance