Overall Satisfaction with Crashlytics
Pros
- Providing stack traces that are useful when users have crashes.
- Tracking crashes per version (app and OS) so we know whether to release a version to everyone instead of a subset.
- Provides trending crsahes/problems if there's a spike in issues so we can get on it quickly.
Cons
- Their app needs to show all the version name or allow us to rotate the app...it trims the name so it's hard to find the right version in the download list.
- Wish their version crash percentage history went back further...would be nice to graph the percent crashes from last year to see how far we've come :-)
- Sometimes Android will have crashes in the middle of Android code...wish Crashlytics did something like Crittercism where it tracked the screens the user visited so we had a better clue; we had to add this info manually.
- Helped bring our crash rate down because we could track the stack traces and occurrences better.
But on Android, Crashlytics is just a lot better in providing good stack traces and having a useful analytics console. It's pretty much the defacto standard on Android...everyone uses Crashlytics. It's even more common to use Crashlytics and the Firebase crash tracking; Firebase does track ANR's a lot better though.
Comments
Please log in to join the conversation