Firebase vs Flurry: What are the differences?
Developers describe Firebase as "The Realtime App Platform". Firebase is a cloud service designed to power real-time, collaborative applications. Simply add the Firebase library to your application to gain access to a shared data structure; any changes you make to that data are automatically synchronized with the Firebase cloud and with other clients within milliseconds. On the other hand, Flurry is detailed as "Build, measure, advertise and monetize your apps". More companies trust Flurry Analytics to understand how consumers interact with their mobile applications than all other app analytics providers combined. Over 80,000 companies use Flurry Analytics in more than 230,000 applications to measure audience reach, engagement, retention, conversions, revenue and more.
Firebase can be classified as a tool in the "Realtime Backend / API" category, while Flurry is grouped under "Mobile Analytics".
Some of the features offered by Firebase are:
- Add the Firebase library to your app and get access to a shared data structure. Any changes made to that data are automatically synchronized with the Firebase cloud and with other clients within milliseconds.
- Firebase apps can be written entirely with client-side code, update in real-time out-of-the-box, interoperate well with existing services, scale automatically, and provide strong data security.
- Data Accessibility- Data is stored as JSON in Firebase. Every piece of data has its own URL which can be used in Firebase's client libraries and as a REST endpoint. These URLs can also be entered into a browser to view the data and watch it update in real-time.
On the other hand, Flurry provides the following key features:
- Harness the power of industry-leading mobile app analytics for free
- Look beyond the download to investigate how users interact with your app
- Learn how, when, where and by what kind of audience your app is used
"Realtime backend made easy" is the top reason why over 318 developers like Firebase, while over 5 developers mention "Most complete and developer/marketing friendly metrics" as the leading cause for choosing Flurry.
According to the StackShare community, Firebase has a broader approval, being mentioned in 859 company stacks & 997 developers stacks; compared to Flurry, which is listed in 24 company stacks and 5 developer stacks.
What is Firebase?
What is Flurry?
Want advice about which of these to choose?Ask the StackShare community!
Why do developers choose Firebase?
- Easy setup214
- Real-time193
- JSON168
- Free106
Why do developers choose Flurry?
What are the cons of using Firebase?
What are the cons of using Flurry?
What tools integrate with Firebase?
What tools integrate with Flurry?
FlurryIt is a rare combination as you guess and there are not a lot of solutions especially in rather-new mobile analytics field that are both easy to integrate for your development team and provides a lot of accurate, relevant data for your marketing department! Great job flurry!
FirebaseFirebase is great, cheap and very flexible. Their docs are very helpful and so is the customer support, but the one thing that is so awesome about firebase is that everything is done in realtime!
FirebaseWe were looking for a solution to find out about all the errors our customers experienced but never informed us about.
FirebaseWe use it for a few things. We use it internally for a few dashboards because it’s actually really nice to have real-time dashboard data with Firebase. We also use it extensively for live order updating. For example, when a shopper is picking your items, you'll be able to go on your order screen. There will be live showing like found or not found or whatever. You'll have live position updating of your shopper on the map. You will have live information of the status of the order like “Nicole is now picking up your order,” and all these kind of things, so you don’t have to reload the page or pull or anything. Just live updates happen natively through Firebase API, which is nice.
FirebaseWe use it for a few things. We use it internally for a few dashboards because it’s actually really nice to have real-time dashboard data with Firebase. We also use it extensively for live order updating. For example, when a shopper is picking your items, you'll be able to go on your order screen. There will be live showing like found or not found or whatever. You'll have live position updating of your shopper on the map. You will have live information of the status of the order like “Nicole is now picking up your order,” and all these kind of things, so you don’t have to reload the page or pull or anything. Just live updates happen natively through Firebase API, which is nice.
FirebaseUsed for storing results of users (malaria predictions) and displaying to user in the app. Although the realtime aspect wasn't huge in this project, it was much quicker to push data elements for each user as firebase elements since they were purely numerical and very small. And again, the idea of familiarity - I've worked with Firebase at previous hackathons, so no need to spend time going through docs, just straight to the coding.
FirebaseFirebase let's us iterate quickly. We've used the Realtime Database to build rich UX features– like push notifications– fast. Likewise, Firebase Authentication and Cloud Functions save us from having to rebuild redundant server infrastructure. Even though Firebase can get pricey, we've saved money in developer time.
FirebaseStill in development, but we will soon (January 2016) be releasing a version that uses Firebase to keep the front end up to date in real time. Certain data are synchronised across RDS and Firebase to optimize the user experience.