Firebase Reviews

Firebase is the best tool for startups that don't have many resources and team members while creating the product. It's straightforward and cheap to have proper authentication and database. Firebase database Is not suitable for a company that needs a SQL database while I recommend it for analytics.

Firebase is great for anyone looking into getting into the mobile app business or ones that already have an app and needs an extra layer of analytics along with additional added features. Firebase helps with troubleshooting the most common issues along with making sure your app remains stable. It goes much further than that if you're interested in running experiments and A/B testing to optimize the user experience you can set that up easily. It gives you the ability to discover a lot of great things about your users and their usability of different features (UI, purchases, engagement, retention, etc.) and helps you identify if the experiment is likely to succeed or not.

If you have a basic app that doesn't have a lot of interactions/touchpoints and you just want some topline numbers, it does an okay job. It's pretty easy to tag your screens, although using Events to tag the interactions can be a bit of a head-scratch.

If you have an App where you want to learn a ton of things about your users, forget it. I'd strongly advise you to choose something else. There are too many constraints in terms of configuring the tagging to capture what you want.

You're going to struggle with adoption across the company. The Interface is terrible (even the Web + App view in Google Analytics is pretty poor) and it's hard to get product/marketing managers to log in and play around with the data.

If you are having an application which requires authentications of users and want to have a central space where you can store all your user data, Firebase is a lifesaver. You can deploy your application once and then control all the operations from the console itself.

In case your applications do not require any authentications and simply available to all the users who download/install it, Firebase might be of less use in that case.

Some scenarios where Firebase is well suited would be specifically to news organizations who regularly send push notifications to a mobile app. If organizations have an IOs or Android app, then Firebase would be suitable for them. It's less ideal for companies that don't send pushes at all, or for companies that want in-depth and highly accurate analytics.

I would recommend Firebase to folks who want to build the prototype of their application in a very short amount of time - say two weeks to a month. You could combine the tools and libraries available and build a functional web app in about a week or two instead of months.

I would then suggest to move to a more stable platform once things are running; the problem is that being a Google product you never know when something becomes outdated or removed as a feature. Things move too fast so you are better off moving to something a bit more stable. Also, Firebase isn't recommended for really large apps; the amount of resources you are going to spend learning and modifying your data structure could be spent on building in a more stable environment.

I think for app development, it is advantageous to use Firebase. It's a real-time, cloud-based database which synchronizes continually across all users. It's really good for creating user authorization for apps which require this. As far as hosting your application, I think it's pretty fast and secure. And it's Google.

Firebase is really well-suited for beginner apps that are run by a small team, with a low marketing budget. The platform gives you the 80 / 20 of mobile app analytics with some cool features such as cloud messaging, A/B testing, in-app messages, crash reporting, etc. While if you are looking to grow and scale, then Firebase is most likely not the solution for you as attribution, cost ingestion, data export, web-to-app, journey banners, and webhooks are more suitable to your plan.

I recommend it for every mobile application that I know solely because it's free. Yes, it's a one size fits all kind of platform so it doesn't get super granular into any specific region of your data but can give you quick and accurate high-level overviews in an instant with extremely easy implementation through cocoa pods.

This is also me talking from a marketer standpoint. From the developer side (I use to be an iOS developer and would always use Firebase as my DB for side projects) it's an absolute dream to work with. Super intuitive with a great front-end UI so you can actually visualize your Non-SQL database with easy and watch it update in real-time. Then with it being one size fits all and owned by Google it has so many integrations and simple one-liners of code to implement complex functions such as file saving, social login, sharing, and more.

Absolutely love Firebase and would recommend for any mobile application and a small team.

Best cloud solution for mobile application development. It made it so easy to build real-time apps. It's the ultimate solution for so many problems that we've been going through for a long time. It is really easy to integrate with the development application. There are a lot of guides and tutorials to learn Firebase in less time.

Well suited for cases when you are dealing with Android or iOS backend and OAuths, or when data storage is a smaller concern than authorizations or push notifications.
Not suited if you have a large user base and each transaction of the data exchange involves several users. It will cost too much.

For any app or service that requires push services, there really isn't anything easier to use than Firebase. Also, the free tier allows a great amount of usage. For us, we have found that our usage has remained below the free tier threshold even with considerable usage as we scale our services. Once we surpass the free tier allowance, the cost will be reasonable, so growth is not really a concern here.

It's best suited for tech and product monitoring, as well as marketing teams to send out user notifications. Less appropriate for a detailed use by tech or marketing, for instance, it will not have pre-set templates for email notifications that can be used by marketing; or it will not have daily summary reports for key parameters that tech can use to circulate amongst key stakeholders etc.—these need to be built on top of Firebase by your own team.

For small projects, or for larger, simple projects that want to take advantage of Firebase's real-time database functionality, Firebase is a great choice -- either the legacy real-time Database or new Firestore. Firebase is not a good choice on its own for workloads that expose a custom RESTful API, services that require complex database operations especially re: search queries and deep joins/population of resources.