Developers constantly have to re-focus: Should we be checking on our application stability or pushing out new features? The issue is that the severity of an issue depends on the context: A huge spike in crashes might be gamebreaking for your application or a non-issue if it only affects one user.
But how can the severity of an issue be presented to a developer?
- One way is to base the health of your application on a single metric; For example, the percentage of crash-free sessions or of crash-free users.
- Another is to provide a single vanity score that encompasses the entire health of an application. When this score is calculated from a number of other metrics, you might lose the valuable insight of underlying scores pointing out any problem areas.
- The final possibility is to give developers multiple individual scores and allow them to decide the relevancy of each area. These granular metrics should be the benchmark for mobile team KPIs.
Embrace follows the third philosophy, looping individual stability metrics into its new Daily Digest Emails. Customers can skip feel-good vanity scores and get straight to the root of the problem: This new email serves as a daily point of comparison on their application’s health.
This summary reports:
- Daily Active Users
- Crash Free Users
- Average Session Length
- Users Distributed By Version
- New Endpoints (when they first appear)
- Top Crashes
Every stat listed on the email links directly to the issue on the Embrace dashboard. That means that, from a crash, you can navigate to the users affected and all of the sessions they experienced—every piece of our dashboard is connected.
On a good day, this means that developers can resume building features without entering our dashboard, knowing their apps are performing well. But, when an especially tough issue arises, the email, paired with the dashboard, presents a powerful tool to help them debug.
Engineering teams are not the only ones who benefit though: Product and QA teams can check on the metrics that matter to them. Version adoption, session lengths, or daily active users all help these teams see if their changes have been positive.
When analyzing your application, it’s better to get all of the data that would inform a stability score rather than just the singular score itself. Embrace makes it easy for you to do that, all without having to enter our dashboard. That way, teams save time when communicating what the issue at hand should be and how to get to the most effective solution.