Embrace vs. Crash Reporting Software: What Are the Differences?

Most mobile app developers use some kind of crash reporting software as part of the development process. Whether it’s a basic, built-in part of your IDE or a specialized service you pay for, you want something that provides mobile app analytics when things go wrong.

You’ll get some help from the basic reports. Having error logs or crash reports is helpful, up to a point. You can look at them, and try to figure out what went wrong, and then try to correct it. You’ll spend a lot of time doing that, in most cases.

Focus where it counts

The thing is, app crashes represent a minimal amount of user problems—about 0.3 percent. Out Of Memory (OOM) exception errors account for about four times as many app shutdowns. And performance issues, which can lead users to abandon your app, come into play about 15 percent of the time. Concentrating only on app crashes means that you’re focusing your efforts on something that affects a relatively small amount of your users, and are ignoring issues that lead to user churn.

Traditional crash reporting software, with its lack of visibility on other issues, doesn’t leave you much choice. How can you fix a problem that you don’t know exists? By looking for the visibility that Embrace provides. We analyze the details of every user session, and let you see exactly what happened.

But we’re not just another data company. Exposing the hidden issues is only half the battle.

We help focus your mobile team on the issues that have the greatest potential business impact. We do things like:

• compare your app to industry benchmarks;

• look at the overall app health trends;

• provide the top user impacting issues;

• show you opportunities to improve the app experience.

Take a look at some examples.

For this e-commerce app, we’re looking at overall app stability, as defined by crashes, OOM errors, and app terminations. 

Mobile app analytics

We also focus on app performance. We time how long it takes from when the user initiates a process—such as start up or purchase—and compare it what industry benchmarks say it should be. If it’s taking too long for users to buy your products, you’ve got problems.

Our health indicator lets you see potential red flag areas. We also provide comparisons of previous versions of your app, so you can tell if you’re getting closer to fixing the problems, or causing others to emerge.

Mobile app analytics

Digging a little deeper, we can look at what percent of devices, and which OS, are encountering the most problems. We also compare that to the percent of your users who are using that device, to see if there is an undue number of problems with a particular device or OS. If there is, that’s another place for you to focus.

Mobile app analytics

Now we drill down to the individual user and session. You’ve got all the relevant information about what the user was doing before the problem. You can look at screenshots to see what they were seeing.

From the aggregate view to the user and session level, Embrace provides a more complete picture that you will get elsewhere. Try it out today!

If you found a few bits of value, please share:
Going Beyond Mobile App Data for Actionable Business Insights
Reducing Mobile App User Churn: A Step-by-Step Guide