We are excited for our latest release focused on taking the first step towards live feedback and continuing to make our SDK have as small a footprint as possible.
Mobile teams are singularly focused on crashes. Understandably so — they are the simplest to identify and diagnose. BUT crashes account for less than 1% of your issues! You still find errors and your users are still complaining.
There are two categories of performance errors that engineers must worry about. The first are visceral issues: those that actually stop the experience altogether and abruptly. These include crashes, which are fairly easy to diagnose and stop, and things like memory issues, CPU pegging, and too many concurrent network calls, which are more difficult.
To put it simply, we love mobile. Mobile is the center of our lives and will continue to be the center. Three simple examples of why: