As an app developer, the health of your app is at the top of your mind. Success depends on many factors, and you want to mitigate as many of those factors as possible.
According to Fast Company, there are five top concerns that keep app developers up at night; (1) a tech giant might move in on your territory; (2) app updates might be buggy; (3) a third-party API might become obsolete; (4) there might be sudden platform changes; and (5) daily download tracking.
As referenced by Fast Company, Crittercism can help you with concern #2 by helping you find potential bugs in your code. A stack trace is the standard modus operandi. However, sometimes it’s not enough, and you need a more detailed report. Crittercism offers a number of advanced features to help you debug your code and triage unknown issues so you can proactively push service updates.
Crittercism allows you to capture and track disruptive crashes that interrupt the flow within the app, even if the error doesn’t result in a crash. We pass handled exception objects to our servers where they will be grouped and symbolicated much like your normal uncaught exceptions.
By placing breadcrumbs in your code, you can get a playback of events in the run-up to a crash. For each session, our libraries automatically store a “session_start” breadcrumb to mark the beginning of a user session, and the most recent 49 breadcrumbs that were left before a crash.
Zero in on app performance by drilling into complex metadata parameters. You can get much finer detail by adding parameters to events such as in-app purchase data, location, time and event that caused an issue, improving conversion and revenue. All personal user data is stripped for increased privacy.
By combining these three key features, handled exceptions, breadcrumbs, and metadata you can increase the potential for app health, app performance, reliability, and revenue.
