When assessing the two solutions, reviewers found Crashlytics easier to use and do business with overall. However, reviewers preferred the ease of set up with Flurry Analytics, along with administration.
Crashlytics "just works" for any size project; it's highly scalable and delivers fresh insight to why your apps are crashing. It's also free.
the user interface could probably be improved, the browser sometimes misbehaves with crashlytics page
I'm using some other crash report and analytics (in parallell, for different clients), and Flurry seems the best. Crashlytics is good for other things, like beta reporting, fast installation, and so on. But, in productive environments, I use, with no doubt,...
The website can be slow at times, and is not easy to use. searching your analytics can be frustrating at times due to UX and performance. Google analytics is simpler and clients tend to know how to us it's web interface.
Crashlytics "just works" for any size project; it's highly scalable and delivers fresh insight to why your apps are crashing. It's also free.
I'm using some other crash report and analytics (in parallell, for different clients), and Flurry seems the best. Crashlytics is good for other things, like beta reporting, fast installation, and so on. But, in productive environments, I use, with no doubt,...
the user interface could probably be improved, the browser sometimes misbehaves with crashlytics page
The website can be slow at times, and is not easy to use. searching your analytics can be frustrating at times due to UX and performance. Google analytics is simpler and clients tend to know how to us it's web interface.