Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Firebase Crash Reporting vs. Crashlytics / Fabric [closed]

I've been using Crashlytics for a few years (now Fabric of course), and am intrigued by the recent updates to Google Firebase.

Has anyone had a chance to use both, and if so... what are your impressions? Did you like one over the other... and why?

Thanks for any info, tips, or general observations in advance.

Have a great weekend. :-)

like image 361
Drew Avatar asked May 27 '16 03:05

Drew


People also ask

What happened to Crashlytics?

In January 2017, Crashlytics and Fabric were acquired by Google. In September 2018, Google announces that Fabric will be deprecated and developers should use Crashlytics via Firebase.

What is crash reporting in Firebase?

Firebase Crashlytics is a lightweight, realtime crash reporter that helps you track, prioritize, and fix stability issues that erode your app quality. Crashlytics saves you troubleshooting time by intelligently grouping crashes and highlighting the circumstances that lead up to them.

What is fabric Crashlytics?

Android Crash Reporting Tools Fabric - Crashlytics Fabric is a modular mobile platform that provides useful kits you can mix to build your application. Crashlytics is a crash and issue reporting tool provided by Fabric that allows you to track and monitor your applications in detail.

Is Sentry better than Crashlytics?

"Crash tracking", "Mobile exception tracking" and "Free" are the key factors why developers consider Crashlytics; whereas "Consolidates similar errors and makes resolution easy", "Email Notifications" and "Open source" are the primary reasons why Sentry is favored.


1 Answers

My advice right now is to depend on Crashlytics for crash reporting until Firebase can further revise features. I've implemented both in some apps, and there are some advantages to Crashlytics. They send email notifications when crashes occur, including for priority changes, and crashes appear very quickly in the interface, within 5 minutes typically.

As it currently stands, Firebase doesn't have crash notifications, and it can take 20-40 minutes for a crash report to appear in the dashboard. A benefit of using Firebase's reporting is that their analytics will create an audience group of crash experiencing users, allowing you to identify and provide a different experience for those users (push notification, welcome screen, coupon code, etc)

Both:

Ability to report logs for crashes to investigate interaction and function

Crashlytics:

~5 minute reporting time

Email notifications

Firebase:

20-40 minute reporting time

Richer user data

Can redact some logged info: "Logged in Chris" could become "Logged in [REDACTED_US_MALE_NAME]"

like image 97
Chris Conway Avatar answered Sep 28 '22 03:09

Chris Conway