Flurry Analytics vs. Pyze

I would encourage a colleague to use Flurry Analytics. Incorporating Flurry Analytics in an app is a simple and straightforward task, and will take the average app developer less than 15 minutes to understand and apply. This amount of time is nothing in the grand scheme of the development of the app, and the return on time invested to incorporate it is great. New tracking features can be added at any time.

• Gives basic tracking capabilities which can help optimize first time experience.
• Lots of high level metrics easily available.
• Benchmarks for many metrics so you can compare yourself within the industry.

• From a programming perspective, there really aren't any improvements that I can think of.
• From the app owner perspective, limits on certain demographics can seem like a hindrance to data collection, but these restrictions are typically imposed by Apple, not by Flurry.

The cost of the product and lack of a competitor that can deliver exactly what we're looking for an app measurement, leads us to be more than likely to renew our use of Flurry. It isn't the most efficient for our particular uses, but the top end app analytic tools out there are far too expensive for us.

For my uses, Flurry is free which makes it way more attractive than the other platforms even on a very big number of monthly events. It also have set reports which are exactly the reports that a marketing person needs without any need of spending a developer time to create them for you, or holding an in-house BI person that works on creating reports.

Incentivized

• Higher engagement ( helped improve first use experience of app)
• Exposed revenue opportunity ( helped establish a link between target demographic Anne their preference for a particular type of EMC PRODUCT)
• Reduced churn rate ( given easy way to set up conversion funnels)