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

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

• 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

• 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

• 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

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

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

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

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

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

• 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

• 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