Countly vs. Firebase Crashlytics

Whether you're planning to include it into a website or a mobile application, this arrangement is simple to implement. The best feature has to be its superb "division," which allows you to delve deeper into your data without using SQL-like queries. On Ubuntu, the free "group version" can act organically aided.

Incentivized

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

• Open-source and Self-hosted - Countly can be completely self-hosted, which makes it really easy to offset costs of a competing service like Segment or Mixpanel for early-stage companies.
• A large number of SDKs and platform support - Countly provides fairly comprehensive support for mobile applications and general tracking. As a result, it's pretty easy to create comprehensive tracking of events for any company.
• Custom queries, access to data - You have instant access to data and extensive customizability which makes this platform fairly easy to use for any purpose of user and market tracking.

Incentivized

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

• No specific thing in mind. All is good except sometimes the customer service lags a little when you have problems setting up the tool.

Incentivized

• 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

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

Countly practically does everything you need it to do. However, it can have challenges of its own sometimes.

Incentivized

Countly have two main elements that make it the better option. First is open sourced so you can edit with code new options and new events, also you can use a variety of plugins depending of the necessities of the users and the objectives of every analysis. The second characteristic is that is very easy to use and even if is open source and the code could seem complex everything is very intuitive.

Incentivized

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

• Allowed me to understand my customer on a deeper level
• Allowed me to tweak my content and sales pages
• Allowed me to better understand my target market.

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