This is part one in a seven part series on how to use Apteligent to implement a collection of best practices from industry leaders called: “7 Best Practices for Optimizing Mobile Apps.”

One of the most important metrics to monitor for a mobile app is the overall crash rate: the percentage of sessions that experience a crash.  To track the health of your app, the crash rate is an important metric to monitor over time and across releases.  According to Apteligent data[1], the best apps have an overall crash rate of less than 0.25%, but 75% of apps across iOS and Android do not meet this standard.  A good rule of thumb to achieve and maintain a 0.25% crash rate is fixing the top ten most impactful crashes each sprint.

In Apteligent, the best place to start is by going to the Crash Summary Page which gives an overview of all the crashes in your app.  To make the biggest impact, focus on the crashes that affect the largest number of users in the latest release of the app.  Here is a simple three-step process to fix the top ten crashes each sprint:

  • 1) Use the Filters at the Top of the Page to Select the Most Important Crashes:
  • a) Time: Select a time range to see all of the crashes that have occurred recently in your app.  We recommend a time range of 14 days to see crashes from the last two weeks.
  • b) Status: Select “Unresolved” to see crashes that have not been fixed.
  • c) App Version: Select the app version of the most recent production version

Fig 1: Apteligent Crash Summary Page

  • 2) Sort by the Most Impactful Crashes

Using the table of crash groups, you can sort crashes by time, number of occurrences, users affected, and the status of the crash group.  Sort this list by “Users Affected” to select the crashes that affected the highest number of users.

  • 3) Assign the Top Ten Crashes Each Sprint

Click on each of the crash groups in the top ten to view details on each crash.  If the app has been connected to a bug tracking system such as Jira, click on the “Create Issue Ticket” button to create a new ticket and assign it  to an engineer to fix in the current sprint.

Fig 2: Apteligent Crash Details Page

[1] iOS, Android