TrustRadius
https://dudodiprj2sv7.cloudfront.net/product-logos/Ai/XD/VAB6G9CA97KE.PNGCrashlytics is our go-toCrashlytics 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.,9,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.,,Google Analytics Premium, Adobe Analytics, Google Search Console, Slack, Tableau DesktopCrashlytics is the defacto standard for Android developersIt'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 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.,9,Helped bring our crash rate down because we could track the stack traces and occurrences better.,Crittercism,Gradle, Jenkins, BambooCrashlytics ReviewWe are using Crashlytics to track both fatal and non-fatal errors that occur in both our iOS and Android native mobile apps.,Pulling the stack trace from an error Bundling errors of the same kind across multiple versions Allowing for caught Exceptions to also be reported as non-fatal errors,Would be great if they could link common system-level exceptions to solutions Sometimes the stack trace is not entirely useful, but not sure what can be done in those scenarios,10,We've been able to track down the root cause of an issue that we were not experiencing during development or testing because it only occurs in certain cases of flaky connectivity. Even after identifying the cause, it was not a reproducible issue, but because we are able to log non-fatal errors also, we could verify that the fix was working in production.,BuddyBuildMobile App DevWe use it a lot for real-time monitoring and for giving us insights that may be lost when the client is otherwise not available. We use it to diagnose potential issues and catch suspect issues without creating a bad experience.,Near real time data Beta distribution is pretty nifty,Calculations of certain percentages can be scary,8,Event tracking helps us identify issues in real time,HockeyApp
Unspecified
Crashlytics
7 Ratings
Score 8.8 out of 101
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>TRScore

Crashlytics Reviews

Crashlytics
7 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 8.8 out of 101
Show Filters 
Hide Filters 
Filter 7 vetted Crashlytics reviews and ratings
Clear all filters
Overall Rating
Reviewer's Company Size
Last Updated
By Topic
Industry
Department
Experience
Job Type
Role
Reviews (1-4 of 4)
  Vendors can't alter or remove reviews. Here's why.
John Doyle profile photo
December 20, 2017

User Review: "Crashlytics is our go-to"

Score 9 out of 10
Vetted Review
Verified User
Review Source
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.
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.
Read John Doyle's full review
Ken Yee profile photo
March 31, 2017

Review: "Crashlytics is the defacto standard for Android developers"

Score 9 out of 10
Vetted Review
Verified User
Review Source
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 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.
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.
Read Ken Yee's full review
Steven Hong profile photo
April 17, 2017

"Crashlytics Review"

Score 10 out of 10
Vetted Review
Verified User
Review Source
We are using Crashlytics to track both fatal and non-fatal errors that occur in both our iOS and Android native mobile apps.
  • Pulling the stack trace from an error
  • Bundling errors of the same kind across multiple versions
  • Allowing for caught Exceptions to also be reported as non-fatal errors
  • Would be great if they could link common system-level exceptions to solutions
  • Sometimes the stack trace is not entirely useful, but not sure what can be done in those scenarios
I can't imagine a scenario where Crashlytics would not be well-suited for use in tracking native mobile app crashes, but maybe it's not as useful for things like Xamarin or React Native (if they even support those).
Read Steven Hong's full review
Junu Kang profile photo
April 05, 2017

Crashlytics Review: "Mobile App Dev"

Score 8 out of 10
Vetted Review
Verified User
Review Source
We use it a lot for real-time monitoring and for giving us insights that may be lost when the client is otherwise not available. We use it to diagnose potential issues and catch suspect issues without creating a bad experience.
  • Near real time data
  • Beta distribution is pretty nifty
  • Calculations of certain percentages can be scary
General mobile app development. How can you live without it?
Read Junu Kang's full review

Crashlytics Scorecard Summary

About Crashlytics

Crashlytics is a mobile analytics tool which helps users find the exact line of code that their app crashed on, providing granular insight into mobile app performance and user experience.
Categories:  Mobile Analytics

Crashlytics Technical Details

Operating Systems: Unspecified
Mobile Application:No