Firebase Crashlytics

Firebase Crashlytics

Score 8.6 out of 10
Firebase Crashlytics

Overview

What is Firebase 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. Crashlytics was acquired by Google in 2017 and is now...
Read more

Recent Reviews

Read all reviews

Reviewer Pros & Cons

View all pros & cons

Video Reviews

Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of Firebase Crashlytics, and make your voice heard!

Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is Firebase 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. Crashlytics was acquired by Google in 2017 and is now offered as part of the Firebase product.

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting / Integration Services

Would you like us to let the vendor know that you want pricing?

15 people want pricing too

Alternatives Pricing

What is Woopra?

Woopra provides real-time customer analytics. It begins by tracking users across digital touch points (website, mobile app, help desk, marketing automation, etc.) and building a comprehensive behavioral profile for each user. These Customer Profiles are Woopra's building blocks, which are used to…

What is SAP Roambi (discontinued)?

SAP Roambi was a cloud-based solution designed specifically for mobile data consumers. Part of the SAP Analytics portfolio, SAP Roambi featured a mobile-first design that took diverse sources into interactive visualizations for users, for publishing reports, dashboards, and analytics for data…

Return to navigation

Product Details

What is Firebase 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. Crashlytics was acquired by Google in 2017 and is now offered as part of the Firebase product.

Firebase Crashlytics Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

 (32)

Attribute Ratings

Reviews

(1-5 of 5)
Companies can't remove reviews or game the system. Here's why
Pankaj Choudhary | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
I am using firebase Firebase Crashlytics to get the actual report of the crashes with the exact line of code. Before Firebase Crashlytics it was very difficult to find the issues. Now, the performance of the project has increased because of the help of firebase Firebase Crashlytics. Firebase Crashlytics also provides all crashes, which we can not afford on our end because of the unavailability of real devices.
  • Can get the device detail an actual state like RAM, Storage, Display Size, etc.
  • Can get the class name and line number where crash occur.
  • Its work in realtime so we can reduce the time of issue finding and resolution.
  • Navigation between the issue listing and details is something difficult to understand for the new user.
  • Pannel takes time in loading may be because of analytics data but it can be reduce.
  • Not provide accurate line number in case of proguarded apps.
If your application is in the initial stage it's very important to use Firebase Crashlytics to get the issues of real devices. Because at the time of development we can test on some devices only so it's very important to watch the behavior of other devices for the app and we can achieve it by Firebase Crashlytics.
  • Devices Details
  • Crash Details
  • Statistics of crash
  • Actually our app is free for all the users so we can say there are no positive or nagative effect on return but our performance has improved after integration of firebase crashlytics.
  • App working smoothly without crashes, Its a positive impact on users.
  • Now we have reduced 80% crash free users to 99% crash free users with the help of firebase crashlytics.
None
20
We ate a Software developers unit and working on a navigation platform so there are a web, ios and android app is available in our solution and we are using the firebase crashlytics in all the three app's. We are very happy with the use of firebase logs reporting and statics.
20
we are the following developers working on separate plateform as a unit to develop a project.
  • Android developers
  • Ios developers
  • Web developers
  • Api developers
We require the same skills.
  • Logs reporting
  • Crashlytics statistics
  • Devices Details
  • In the earlier stage we got the number of crashes and to resolve that problems we implemented the firebase crashlytics.
  • It would be good if we can test the same issue on same device virtually.
Because its fulfilling our basic and necessary requirements that can be an only and enough reason to renew the subscription.
Score 7 out of 10
Vetted Review
Verified User
It helps us in monitoring our app and helps us test the beta versions with the complete track of usage and crash reports; we can make better decisions by fixing the bugs and providing more stability to our app.
  • Tracking the complete crash points in realtime.
  • Real time app usage and screen time.
  • Complete crash report for all version of Android & iOS.
  • Sometimes UI of Firebase Crashlytics is quit difficult to understand for new users.
  • There can be a proper discretion for all the features that is offered.
  • There can be api crash report also.
Firebase Crashlytics helps us in tracking our app's performance and crash-points. This helps us improve the app performance and provide a better user experience. Also, we get to know what are the areas that user liked the most from the screen time that user spent while using the app. Sometimes when we want to set up Crashlytics to test small features, it becomes complex to set it up with separate screens.
  • The complete app crash report.
  • Crash report on different os versions (Android & IOS).
  • Realtime usage tracking of the app.
  • It has help me in improving my app stability and has helped a lot in improving the UI.
  • Also, sometimes its quite interesting to understand the app usage, and it helps us in making better decisions.
Truly speaking, it is also a quite good tool for crash reports, but Firebase Crashlytics was better to use when you are using the Firebase Realtime database as your DB, so the integrations become much easier.
Amazon S3 (Simple Storage Service), Firebase, Keka HR
Ben Gelsey | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
At Instructrr, we use Crashlytics to monitor our fitness iOS app for any crashes. In the event of a crash, email notifications get sent to all of our developers and the CEO of the company. This is invaluable to us because often our userbase manages to use the app in ways that our developers don't, which sometimes leads to crashes that we can both detect and quickly fix due to the realtime notifications from Fabric.
  • Detecting Crashes
  • Showing backtraces to the exact line of code causing the crash
  • Fine-grained Notifications
  • Improve the SDK installation documentation
  • Simplify the migration from Fabric.io to Firebase
  • Improve the UI, currently it feels fairly old & clunky
Crashlytics is the go-to mobile crash/analytics tool for the entire industry. Now that it is 100% free across all usage levels, even with enterprise feature usage, there is honestly no reason to go with any competitors. Crashlytics had the first mover advantage and has continued to stay ahead of the competition, even after its 2 acquisitions (first by Twitter, then by Google). The only realistic competitor to Crashlytics is Instabug, but as soon as you go beyond their most basic features you are looking at a $124 to $499 per month bill. For all of the apps I have worked on, that has never been worthwhile.
  • Fix bugs within hours rather than days or weeks
  • Retain users longer by reducing their frustration due to crashes
  • Keep management happy that our app is stable & bug-free
As mentioned previously, the only realistic competitor to Crashlytics is Instabug (backed by Y Combinator in the W16 class). While Crashlytics is focused on actual crashes, Instabug's main innovation is in collecting feedback from users for non-crash bugs. While non-crash bugs are a substantial category of bugs, Instabug's pricing is quite steep. As soon as you go beyond the most basic features your monthly bill spikes to $124 - $499 per month, whereas Crashlytics is 100% free (for all usage levels and all enterprise features). Based on this, I've never tried Instabug because the ROI just wasn't there.
December 21, 2017

Crashlytics is our go-to

Score 9 out of 10
Vetted Review
Verified User
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.
  • 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.
Ken Yee | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
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.
  • 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.
Return to navigation