Flurry
21 results found
-
The UI could be a bit better, more like Firebase or how Fabric was.
Everything works well and is easy to setup. And it's free.The UI could be a bit better, more like Firebase or how Fabric was.
5th ranked -
Flurry has a better UI than Firebase and paramerters are easy to use.
Easy to use parameters. Better interface easier than Firebase.
5th ranked -
Flurry integration is easier than GA.
Much easier to integrate than Google Analytics. We switched to Flurry because it is so easy.
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 -
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 -
Flurry needs to support Push notifications better. Either with documentation or onboarding marketing teams better.
marketing team able to create targeted (push) campaigns (Countly best because they help Marketing team with everything; Flurry worst because Braden didn’t want to teach Marketing; no hand holding available for marketing team)
5th ranked -
Need to make integration simple
quick and easy integration (Firebase best because Braden and team have already been using Firebase’s push notifications component; Clevertap worst because of React Native issues)
5th ranked -
Ability to send exisiting & potential users to any location within our iOS & Android app via Dynamic Links.
Looking for the equivalent of Firebase Dynamic Links
5th ranked -
Firebase's limit on parameter's per event is 10. This is not enough.
its easy to open a dashboard and see the different types of tools and events and what not. But when you get the kinks out of it, like: you can only track 10 parameters at once in Firebase in the free version - these arent things that are evident; you have to stumble upon those issues.
5th ranked -
Having a fulltime support team is a plus.
Firebase very difficult to contact and get support
5th ranked -
Flurry's ability to compare apps side-by-side is very important. Need to be able to see app-level & company-level stats.
Firebase account could not be set up in a way to view app level and company level statistics easily. Difficult to compare apps side by side.
5th ranked -
Flurry should consider expanding its event limit beyond 500.
Firebase Event Limits hamper their business analytics. Very "rigid"
5th ranked -
Appsee's UX/UI is very good and their screen recording features are very cool.
Appsee screenshare issue followed by their acquisition. Appsee would not renew their contract forcing them to look elsewhere. Said UX/UI and Screen recording features were "cool to look at and show people" but not very useful and gimmicky in practice.
5th ranked -
Having data accuracy issues since moving to Firebase
Was using Fabric, migrated to Firebase, had difficulties with data accuracy
5th ranked -
Using Push on Urban Airship is expensive. Flurry being free makes our decision process easier
Urban Airship is "Incredibly Expensive" to send push notifications
5th ranked -
Flurry makes it easy to view iOS & Android app data side-by-side.
Firebase made it difficult to view their iOS and Android apps side by side
5th ranked -
Need more advanced analytics features and settings to look at weekly/aggregate data. Data needs to be continuously accessible.
You cannot set different time spams for the logs and then you cannot see the average for one week or for one month. You cannot export all the data, basically; you can export the events themselves and the number of events, but you cannot export the attributes, the percentage of users that did the event in one way, the percentage of users that used the event in other way. Crashlytics Answers is too basic. We would like to have a bit more insight and to have a bit better and easier access to data, and actually haveaccess to data, because…
5th ranked -
Keep Flurry SDK small. Firebase's SDK is too large.
Footprint too big "users were complaining about memory usage"
5th ranked
- Don't see your idea?