TrustRadius
Crashlytics is our go-to
https://www.trustradius.com/mobile-analyticsFirebase CrashlyticsUnspecified9.111101
John Doyle profile photo
December 20, 2017

Crashlytics is our go-to

Score 9 out of 101
Vetted Review
Verified User
Review Source

Overall Satisfaction with Crashlytics

Crashlytics is the primary tool we use to monitor and obtain insight into native app crashes. Our developers prefer it over every other similar tool on the market and have told me that they believe it is the most accurate and is easy to implement. We use it across all of our native app projects.
  • It has a great reporting interface to monitor crashes and affected users.
  • Setting up breadcrumbs to provide better insights around crashes is simple.
  • Easy for a non-developer like myself to jump in and figure out things quickly.
  • An easier way to understand app version adoption rates alongside crashes.
  • I feel like the platform keeps trying to become more of an all encompassing analytics platform and should stick at what it does best—crash monitoring.
  • Now that it has been acquired by Google, I hope things like navigation and implementation don't become more cumbersome as has been the recent case with Google Analytics.
  • Allows us to easily share crash data with clients.
  • Provides confidence to our developers and project teams by having trust in the data that is being reported.
  • Allows us to quickly and efficiently address fatal crashes.
Based on what our developers have told me, Crashlytics is better than anything else out there. I personally have worked with Flurry for event and crash monitoring, and my experience was terrible. I know some project teams have tried some alternatives in the space that I don't recall, but they didn't stick and we have always fallen back on Crashlytics. I'm now just hoping that it doesn't crumble under Google.
Crashlytics is well suited within any native application in order to understand where and why crashes may be happening, and how many sessions and users are affected by crashes. It is also a great tool to establish a crash free baseline that needs to be kept by the development team. I don't believe it is well suited for tracking the bigger picture around your users' in-app behavior.