Flurry vs localytics?

Question

what are the advantages and disadvantages in using Flurry or Localytics?

Answer 1

I can't answer about iOS, but the Android libraries for Flurry had a very half-baked feel to them when I tried them out about 3 months ago. There's a lot less power in their stats reporting and drilling down through the data can be like pulling teeth.

Additionally, I was getting wildly inaccurate session counts in a small closed beta test of my app (1000 sessions reported in a few minutes from one device). When I contacted Flurry support, it took them nearly a week to get back to me and then all I got was a fairly useless stock response. That alone knocked them straight off my list of potential analytics providers.

I've used Localytics on Android for hundreds of thousands of total installs at this point and am quite happy. Android gets treated as a first-class citizen (rather than feeling like a bolt-on on Flurry or even Google Analytics), and they have a pretty nice looking UI with a lot of good drilldown controls.

Answer 2

Both services are free and both services provide the same basic functionality of providing app analytics (e.g. number of users, type of devices, how the users are interacting with the app, etc.).

I have used both services for Android, although I am currently using Localytics because the Localytics library is open source. The Flurry library is closed source. Open source has the advantage that you can modify the library, as well as see exactly what the library is collecting.