Not surprisingly, users hate it when their mobile apps crash. And there’s pretty much nothing worse for mobile app developers than an app that crashes in ways that are difficult to understand and hard to replicate. Developers and product teams often struggle to figure out exactly what’s going wrong, how pervasive the problem is, and how to fix it quickly and definitively. They need a way to know which crashes to fix first and how to debug them quickly.
(To see the new Mobile Crash Analysis features in action, watch the video demo at the bottom of this post.)
Meet Mobile Crash Analysis
Given the importance of delivering great mobile apps, New Relic really wanted to design a user experience flexible enough to address a wide range of needs around crash reporting. So, voila! We present to you: Mobile Crash Analysis.
New Relic is using our advanced analytics capabilities (which you may have explored in the user interface for New Relic Insights) to transform New Relic Mobile, our curated mobile performance monitoring product, so that developers can evaluate the impact of a crash to prioritize it and the context of a crash to reproduce it.
For a bit more background, Insights uses what we call event-based data. Each event—a mobile session, for example—will have a long list of attributes associated with it as part of New Relic Mobile’s out-of-the-box instrumentation. These attributes provide a way for New Relic customers to ask different questions about their data and to slice it in different ways.
In New Relic Insights, customers can create dashboards of various charts using this data. With Mobile Crash Analysis, we have brought the same Mobile events and their attributes into the New Relic Mobile product itself. The extensive set of attribute data and the new user interface together allow vast flexibility for customers to facet and filter crashes in powerful new ways.
Mobile Crash Analysis was released on October 31, and is available to all of our customers. Log into New Relic, head to the Mobile tab, select one of your apps, and look for the “Crash analysis” menu item on the left side of the screen. Mobile Enterprise customers will see new crash rate charts, filtering and grouping, custom and default attributes, and interaction trails for every occurrence. Other customers will see the new crash rate charts, stack traces, and default attributes for every occurrence.
Cool stuff you can do with Mobile Crash Analysis:
- High-crash screens: Find out the most common place in your app where users experience crashes. Group by “Last Interaction” to see the screen most commonly loaded before a crash.
- High-crash code: See the most common place in the code associated with crashes. Group crashes by file (“Crash Location File”) and method (“Crash Location Method”).
- Version comparison: Group crashes by App Build or App Version, or filter first to a specific crash type (“Crash Location”) and then compare it across versions of the app.
- Quick response: Filter to crash occurrences associated with a particular user (using a custom attribute) for a more efficient support response. Fix that user’s crash, filter to that “Crash Location,” and group by user ID to see which other users experienced the same crash and might appreciate upgrading to your latest app build.
- System updates: Track which store is experiencing the most point-of-sale crashes, and view device, app version, or connection attributes for that store (using “City” or a custom attribute for store ID).
- View in Insights: Hover over a faceted, filtered crash chart and click “View in Insights” to pull up that chart and its specific query in the Insights UI.
(For more information on the cool stuff, read the New Relic documentation.)
Mobile Crash Analysis in action
For an idea of how Mobile Crash Analysis works for identifying high-crash screens (the first example above), check out this animated GIF:
(For a more detailed walk-through of Mobile Crash Analysis, watch the demo video from FutureStack16 San Francisco below, or visit the Crash Analysis Tips and Tricks topic in the New Relic Discussion Forum. Feel free to add comments as part of that topic. We are excited to get your feedback!)