Crashlytics is the defacto standard for Android developers
March 31, 2017

Crashlytics is the defacto standard for Android developers

Ken Yee | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with Crashlytics

It's being used for our iOS and Android apps to track crashes in the field and from QA. I'm one of the Android developers so I'm more familiar with how it works on Android. It provides useful crash reporting including stack traces so we can quickly find and fix crashes that only happen in the field (which is needed because there are so many Android devices and versions that you can't possibly test on all possible platforms). It also tracks crashes per version so we can decide when to release a new version after we soak test it w/ a small percentage of our users.
  • 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.
  • Their app needs to show all the version name or allow us to rotate the 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.
Compared it with Crittercism on a Xamarin project a while back and on that platform, Crittercism was the best.
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.
Crashlytics is almost a defacto standard in the Android world for tracking crashes in the field. I've used it on the last 4 Android projects I've been on.
It's not as helpful on iOS' stacktraces but I'm not sure if anything would be better because iOS stack traces are from ObjC code which is not as useful as Java stacktraces.