Firebase Crashlytics vs. Flurry Analytics

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

I would encourage a colleague to use Flurry Analytics. Incorporating Flurry Analytics in an app is a simple and straightforward task, and will take the average app developer less than 15 minutes to understand and apply. This amount of time is nothing in the grand scheme of the development of the app, and the return on time invested to incorporate it is great. New tracking features can be added at any time.

• 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

• Gives basic tracking capabilities which can help optimize first time experience.
• Lots of high level metrics easily available.
• Benchmarks for many metrics so you can compare yourself within the industry.

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

Incentivized

• From a programming perspective, there really aren't any improvements that I can think of.
• From the app owner perspective, limits on certain demographics can seem like a hindrance to data collection, but these restrictions are typically imposed by Apple, not by Flurry.

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

The cost of the product and lack of a competitor that can deliver exactly what we're looking for an app measurement, leads us to be more than likely to renew our use of Flurry. It isn't the most efficient for our particular uses, but the top end app analytic tools out there are far too expensive for us.

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

For my uses, Flurry is free which makes it way more attractive than the other platforms even on a very big number of monthly events. It also have set reports which are exactly the reports that a marketing person needs without any need of spending a developer time to create them for you, or holding an in-house BI person that works on creating reports.

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

• Higher engagement ( helped improve first use experience of app)
• Exposed revenue opportunity ( helped establish a link between target demographic Anne their preference for a particular type of EMC PRODUCT)
• Reduced churn rate ( given easy way to set up conversion funnels)