Firebase Crashlytics Reviews & Insights

We use Firebase Crashlytics to collect crash reports from our Mobile, Android, and macOS apps and provide them through one unified, easy-to-use interface that quickly allows us to see what the crashes are, how often they are occurring, when they have occurred, and the platforms and configurations that these crashes are happening on.

Firebase Crashlytics is a no-brainer if you are already using any of the other Firebase suite of products, as its integration is very easy if you are already using these in your app. If you have cross-platform Android, iOS, and macOS apps, you should also consider Firebase Crashlytics to provide a unified across your platforms. If your app is only on Android or only on Apple, then you may be better off remaining with the default Apple Developer or Google Play Developer Console crash collection experiences.

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.

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.

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.

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.

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.

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.

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.

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.

We are using Crashlytics to track both fatal and non-fatal errors that occur in both our iOS and Android native mobile apps.

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).

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.

General mobile app development. How can you live without it?

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.

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.