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.

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

Incentivized

• Flurry can track in-depth metrics across your app. This allows us to see every type of interaction our app users are performing.

• Navigation between the issue listing and details is something difficult to understand for the new user.
• Pannel takes time in loading may be because of analytics data but it can be reduce.
• Not provide accurate line number in case of proguarded apps.

• There is no option to choose a timezone which will allow me to compare their data over other systems in other time zones.
• Could be nice to have more reporting screening options.

Incentivized

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

Good user acquisition tracking
Sdk integration is super easy for both iOS and Android
Need it
Need to support more customized dashboards / reporting (example - set up a dashboard specifically to see users engaging with a new feature recently launched)

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

Truly speaking, it is also a quite good tool for crash reports, but Firebase Crashlytics was better to use when you are using the Firebase Realtime database as your DB, so the integrations become much easier.

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

• Fix bugs within hours rather than days or weeks
• Retain users longer by reducing their frustration due to crashes
• Keep management happy that our app is stable & bug-free

Incentivized

• Tracking the number of times a user taps a help button can help to improve the app design. Perhaps the app is not as intuitive as first thought, and improvements based upon where in the help feature a user taps will lead to improvements in the app design to make it more intuitive.
• Tracking the number of times certain app features are used, or the amount of time spent within a given activity in the app can help to streamline an app - improve upon features that are used more frequently while eliminating less popular activities.
• Tracking time spent within an app can give an idea as to how popular the app is.