Firebase Crashlytics vs. Sentry

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.

Incentivized

[Sentry] is honestly an amazing product. It allows us to detect errors in real time complete with stack traces and any extra accompanying information the developer wants to provide in the alert. With the alerting into Slack it has allowed us to quickly triage and tag in people who need eyes on a specific issue. It would be really useful in any Saas product environment.

Incentivized

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

Incentivized

• It collects very detailed information on problems that happen to our users while using the platform
• It supplies very good tools in order to aggregate the collected data and analyze it
• It integrates with Slack, making it easier to "monitor it in real time"

Incentivized

• Improve the SDK installation documentation
• Simplify the migration from Fabric.io to Firebase
• Improve the UI, currently it feels fairly old & clunky

Incentivized

• if we could decrease the costing via some kind of sampling of errors.
• sometimes same error is in loop and Sentry will count all the events for pricing if there is any way this can be reduced.
• self hosted capabilities or using own storage to reduce cost.

Incentivized

Because its fulfilling our basic and necessary requirements that can be an only and enough reason to renew the subscription.

It is very easy for non-developer staff to use the Firebase Console and gather information for the development team. Developers will find it straightforward to integrate Firebase Crashlytics into new or existing codebases using Google's in-depth developer documentation. I cannot think of an easier cross-platform solution to use, and because of that I wish it supported more platforms!

Incentivized

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.

Incentivized

We actually ended up using both because New Relic is a more robust overall IT infrastructure monitoring product. However, sentry is more developer oriented on the backend and more client friendly on the front end as far as showing results and the dashboard etc. It can provide product level insights that New Relic does not.

Incentivized

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

Incentivized

• Error tracking is a must in any modern dynamic website or app. By looking into the error notifications I'm able to fix errors before anyone even has a chance to complain about them!
• Surprisingly, many website issues aren't showing up in Sentry, because they don't trigger exceptions. I'm interested in seeing if I can use Sentry to catch manually-triggered exceptions for "undesirable states" that my website can find itself in. Of course, that means I have to figure out how to have my client code recognize that it's in an undesirable state...

Incentivized