Flurry
288 results found
-
Improve UI of Android App
Improve UI of Android App
5th ranked -
Event history when of churned users. Make it easy to capture events prior to app uninstall.
This is the best platform for app analytics and monitorong KPI's, easy client side integration, and most importantly it's free and intuitiveEvent history of day 1 churned users. We haven't yet figured out how we can detect what a churned user did in app before uninstalling, this is really beneficial to identify common patterns of behaviour or app events for users uninstalling the app on day 1. I think funnels might be useful for this but currently in the processes of figuring that out. Also I have noticed after looking at random sessions is that some of those sessions have…
5th ranked -
Improve UI/UX
Great service and ProductImprove ui and ux
5th ranked -
Improve app experience
Real time data is good and accurate. Improve your app experience
5th ranked -
Cross search in custom event with multiple parameters
UI friendly, is free with remote config. Cross search in custom event with multiple parameters
5th ranked -
Woopra funnels are better than Flurry
Flurry should look into what makes Woopra's funnel analysis highly rated
5th ranked -
Pendo UI is easier to use than Flurry
Pendo does a good job of providing tooltips to walk you though it's UI
5th ranked -
Pendo vs Flurry head-to-head shows Pendo has an upper hand
Aggregated event reporting (ie feature usage) (Pendo better); Granular individual (client, employee) app usage reporting (Pendo better); Funnels (Pendo better) ; Ease of use (Pendo better); In app messaging (Pendo better)
5th ranked -
Flurry documentation is not as good as Fabric's. Not easy to find info about custom events
Found documentation for Fabric easier to use since it combines both official and community based on Stackoverflow etc; he attributed this to Fabric’s larger user base; for Flurry to find info about custom events he had to use the official site only and use the topic links in left hand margin to find what he wanted; he didn’t see a search feature
5th ranked -
It would be nice for Flurry to support a Web SDK.
Mixpanel is more useful across the org as it provides both web and mobile data. Having a web SDK in Flurry would be useful.
5th ranked -
For Flurry to move upstream they need to add better behavioral analysis.
Contrasted Flurry as a tool for “product insight” vs Mixpanel for “marketing insight” when “going from launching to growth hacking”
5th ranked -
Difficult to configure Push during Flurry implementation
Had problems configuring push during Flurry implementation experience; works fine during test but not on live app
5th ranked -
Continue showing event data on Flurry's mobile app
Flurry's mobile app shows event data which is very valuable. Facebook's analytics app only shows analytics dashboard data and not event data.
5th ranked -
Flurry's real-time data is delayed
Fabric's analytics dashboards and event data showed up in real-time. Flurry's data was always delayed, specifically event data (12-24 hours). This needs significant improvement.
5th ranked -
Fabric dashboard UI was amazing
Flurry should work towards making their UI even better. It is better than Firebase overall but not as good as Fabric was.
5th ranked -
Flurry documentation is good and features match up to Mixpanel.
Decided to switch to Flurry after visiting the Flurry site and reading the docs; “Flurry has all the features of Mixpanel and it’s free; the SDK is super simple to integrate”; “all I really care about is events”
5th ranked -
Price is an important factor in decsion making for analytics tools
Looking for a Firebase replacement and Flurry & Mixpanel were identified as alternatives. Mixpanel was eliminated from his short list because it’s “too expensive” costing “several hundred $ per month”.
5th ranked -
Need to anonymize user IP to comply with GDPR
Flurry does not support the ability to anonymize user IP to comply with GDPR. This a a feature that Firebase allows and was the main reason to decide against Flurry.
5th ranked -
Data speed for Flurry is a real limitation
Flurry consistently showed reporting delays; known events were slow to appear in Flurry
5th ranked -
Flurry integration is simple
Flurry’s integration was simple; “it’s just one line”
5th ranked
- Don't see your idea?