Flurry Analytics is one of the world’s most recognized and adopted mobile app analytics solutions. It’s easy to use, powerful and completely free. Designed to help product, development and growth experts build apps users love, Flurry helps improve app engagement, run a data-driven product roadmap, boost user acquisition efforts and more. Flurry also includes crash reporting, push notification management and remote configuration.
Flurry Analytics provides real-time metrics for iOS and Android apps around usage and retention as well as geographic, demographic and technographic insights. Tailor Flurry Analytics to your app by adding up to 500 custom events as well as unlimited parameters for uncompromised detail.
Flurry also delivers on-demand, fast querying for easy slice-and dice to explore and segment your audience like never before. Finding key insights shouldn’t require you to be a SQL expert, wait to export data into a different system or pay upcharge fees for cloud usage. Conduct audience analysis, build funnels and view user paths like never before.
View metrics by groups of apps or individually, and even compare iOS versus Android versions of your app side by side. Integrating Flurry’s lightweight SDK is simple and takes just minutes.
Eric S.
Advanced user of Flurry Analytics
★★★★★
Flurry is a lightweight, straightforward way to see what users are doing in my app
What do you like best?
It's easy to set up, fairly lightweight, and straightforward to use. I can see what users are doing in my app. And then secondarily, higher level tracking like how many sessions show me app activity in general.
Also their web and mobile iOS apps are easy to navigate and keep me updated daily.
What do you dislike?
There are a few things I don't use. I've tried to use the watchOS tools, and they don't seem to work very well. So I don't use those even though I spent some time trying to get it to work.
Recommendations to others considering the product:
Try it out. It's easy to set up and fairly lightweight. It's just a matter of including a library and a few calls. There isn't a lot of baggage. It doesn't have a lot of dependencies on other libraries which would add both load time and binary size to the app.
What problems are you solving with the product? What benefits have you realized?
When I know what features my users are using or what they aren't using, then I know whether it's worth my time to further improve them. There have been things I thought were super powerful. That a user would love. And it turns out they aren't discovering them, and probably aren't finding them as useful as I thought. So I'm not working on those features anymore.
Review source: G2.com
