Firebase Crashlytics vs. Flurry Analytics

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.

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.

• Can get the device detail an actual state like RAM, Storage, Display Size, etc.
• Can get the class name and line number where crash occur.
• Its work in realtime so we can reduce the time of issue finding and resolution.

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

• Sometimes UI of Firebase Crashlytics is quit difficult to understand for new users.
• There can be a proper discretion for all the features that is offered.
• There can be api crash report also.

Incentivized

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

As mentioned previously, the only realistic competitor to Crashlytics is Instabug (backed by Y Combinator in the W16 class). While Crashlytics is focused on actual crashes, Instabug's main innovation is in collecting feedback from users for non-crash bugs. While non-crash bugs are a substantial category of bugs, Instabug's pricing is quite steep. As soon as you go beyond the most basic features your monthly bill spikes to $124 - $499 per month, whereas Crashlytics is 100% free (for all usage levels and all enterprise features). Based on this, I've never tried Instabug because the ROI just wasn't there.

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

• Allows us to easily share crash data with clients.
• Provides confidence to our developers and project teams by having trust in the data that is being reported.
• Allows us to quickly and efficiently address fatal crashes.

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.