Crashlytics: Old but Gold
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 …
Firebase Crashlytics
Firebase Crashlytics
Overview
Recent Reviews
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!
Pricing
View all pricingN/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?
9 people want pricing too
Alternatives Pricing
What is Google Analytics?
Google Analytics is perhaps the best-known web analytics product and, as a free product, it has massive adoption. Although it lacks some enterprise-level features compared to its competitors in the space, the launch of the paid Google Analytics Premium edition seems likely to close the gap.
What is Amplitude Analytics?
Amplitude Analytics is an analytics platform for mobile and web. It is designed to help organizations segment users and analyze funnels, retention and revenue.
Features Scorecard
No scorecards have been submitted for this product yet.Start a Scorecard.
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 Systems | Unspecified |
|---|---|
| Mobile Application | No |
Comparisons
View all alternatives
Reviews and Ratings
 (24)
Reviews
(1-5 of 5)- Popular Filters
Companies can't remove reviews or game the system. Here's why
May 15, 2019
Crashlytics: Old but Gold
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
December 21, 2017
Crashlytics is our go-to
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.
April 17, 2017
Crashlytics Review
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
April 05, 2017
Mobile App Dev
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
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.