Countly vs Firebase Crashlytics

Likelihood to Recommend

Countly is wonderful. It mhas affordable options for startups that are experimenting with event and market-tracking services that can't afford more expensive services but do have the cloud credits to operate Countly. For later-stage companies that have the money, but not the time to set up a service like this, a service like Amplitude, Segment, or Mixpanel may be a better alternative.

Read full review

Fedor Paretsky

Co-Founder/CEO

aspace, Inc.Computer Software, 1-10 employees

View all 2 answers on this topic

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.

Read full review

Ken Yee

Android Architect

KAYAKInternet, 51-200 employees

View all 5 answers on this topic

Pros

Great tool for mobile and web analytics
Open source

Read full review

Verified User

Director in Marketing

Internet Company, 51-200 employees

View all 2 answers on this topic

Detecting Crashes
Showing backtraces to the exact line of code causing the crash
Fine-grained Notifications

Read full review

Ben Gelsey

Software Developer

InstructrrHealth, Wellness and Fitness, 1-10 employees

View all 5 answers on this topic

Cons

Bad UI - The UI is quite outdated and poorly designed, which was one of the principal reasons for us moving away from Countly.
Some poor documentation - 3rd-party documentation and tutorials for some of their mobile SDKs are better than Countly's own documentation.
Server requirements can be a bit high - For startups with trial credits on cloud computing services, this may not be a problem. Otherwise, Countly can get as expensive as hosted services like Segment and Mixpanel.

Read full review

Fedor Paretsky

Co-Founder/CEO

aspace, Inc.Computer Software, 1-10 employees

View all 2 answers on this topic

An easier way to understand app version adoption rates alongside crashes.
I feel like the platform keeps trying to become more of an all encompassing analytics platform and should stick at what it does best—crash monitoring.
Now that it has been acquired by Google, I hope things like navigation and implementation don't become more cumbersome as has been the recent case with Google Analytics.

Read full review

Verified User

Team Lead in Research & Development

Marketing and Advertising Company, 51-200 employees

View all 5 answers on this topic

Support Rating

Countly 7.0

Based on 2 answers

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

Read full review

Verified User

Director in Marketing

Internet Company, 51-200 employees

View all 2 answers on this topic

No score

No answers yet

No answers on this topic

Alternatives Considered

Matomo has poor integrations and SDK support compared to Countly. It is also significantly harder to set up compared to Countly. There have also been complaints about Matomo having security flaws. Additionally, Matomo seemed to lack common analytics platform features, like segmentation, and tracking/downloading raw data. These features are very easy to use in Countly and are usually a necessity for most companies.

Read full review

Fedor Paretsky

Co-Founder/CEO

aspace, Inc.Computer Software, 1-10 employees

View all 2 answers on this topic

BuddyBuild's crash reporting tool is a far cry from Crashlytics, and the interface is also not nearly as good.

Read full review