Google Firebase Reviews

We use Firebase for understanding crashes and tracking analytics about our users, which supports marketing, development, and distribution purposes.

Firebase has been helpful in providing analytics and crash insights. It still needs more detail for larger scale applications.

Crashlytics is the best feature in Firebase.

They could add a session replay to better understand how a crash or bug happened.

We have been using Firebase for maybe six or seven years.

I do not remember any major issues with stability while using Firebase.

Firebase is easy to scale.

The support team responds rapidly. There is a good community with many solutions available through shared videos on YouTube and blog posts.

I have previously worked for Huawei and Google Analytics and have experience with their customer service.

The initial setup is very easy, and the guidelines and tutorials are helpful for developers, even junior developers.

I don't know the current prices, however, it is probably average compared to others in the market.

We were considering Instana and Sentry for different business needs and have arranged meetings to decide further.

For startup or personal applications, I strongly recommend Firebase. However, for big businesses or large domains, I suggest using a different tool.

I'd rate the solution ten out of ten.

Google Firebase is not an alternative to Vercel. For my job, I use the tool to host the Next.js app application. The option to host the Next.js app was launched a year ago.

I have been using Firebase for some of its features, like its cloud functions and authentication kind of purpose. We cannot compare Google Firebase with Vercel.

The most valuable feature of the solution stems from the fact that its storage can be easily used in our mobile applications. The tool can be used for cloud messaging. The push notifications on iOS and Android services are very easy to use.

Google Firebase is a very big application.

In our company, we are actually using a small part of the application, so I do have challenges, but we have online communities for Firebase. Google's support is very low, and it takes a lot of time. The tool's support requires improvement.

I have six years of experience with Google Firebase. I am a customer of the tool.

I have not faced any stability issues with the product.

The product offers high scalability features, but the cost is very high on a large scale. The tool has some mechanisms for improvements, but it is costly.

I rate the technical support a seven out of ten.

Neutral

Actually, there are some other mechanisms in the tool that we can avoid. We can use many other services. If we are hosting and using Google Firebase to send SMS, it will cost a large volume. If we choose the local providers, we can get a tool similar to Google Firebase at a very low rate.

The authentication part in the product is very easy to use, but for custom development, we have to use the product manually, making it a reason why we don't have to use the authentication feature.

The tool has many features, but sometimes, using all its features can be a little difficult, and it is not easy to implement. You need to read the documentation to figure out the process for using the features.

I recommend Google Firebase for cloud storage and cloud communication to others.

I rate the tool a seven out of ten.

I mainly use authentication, database, notifications, and remote config. Most of the key features of Firebase.

The authentication. It's a managed product that supports all types of authentication and has a generous free trial. They give a very big free credit to start with.

Firebase Analytics is good enough, but I prefer to use Google Analytics directly by inserting their tag in my code.

We don't use their app distribution product. It's okay, but not that useful.

They lack a SQL database. It would be great to have that feature added.

Like PlanetScale. They have a Firebase database as well as a real-time database, but no SQL database.

I have been using it for three to four years now. 

It's stable. No issues so far.

All students use it, especially for building side projects. Maybe not everyone uses all features, but Firebase authentication is widely used.

Firebase authentication is very scalable. But for the Firestore database, people say you can get a big bill when you scale up.

We didn't experience that because we didn't reach that scale, but their pricing plans indicate it can get very expensive.

Cloud Storage is good, but I switched to Cloudflare R2 because to the cheap pricing plans. However, at scale, Firestore can have issues with concurrent writes, like exceeding rate limits.

We did reach out to them for GCP, but not for Firebase. 

The initial setup is very easy. Even for a beginner. Their documentation is good, and there are a lot of helpful videos on YouTube.

The pricing plans indicate it can get very expensive.

I would definitely recommend it to others. It is very easy to learn. 

Overall, I would rate it a nine out of ten.

I chose Google Firebase because it provides an easy way to authenticate. It offers a lot of authentication services and libraries. It is easier to use, allowing authentication directly from the front end without interacting with the back end. For more advanced use, it can also integrate with the back end. It supports most social logins and offers a free tier with features like email sending for sign-up confirmations and OTP authentication, which can be costly. The solution is user-friendly for developers and good for our company’s authentication needs across all applications.

The authentication features have made things a lot easier for our organization. About five years ago, developers had to create authentication systems from scratch. Now, services like Google Firebase provide secure and accurate authentication solutions. We can implement authentication quickly by following their documentation.

The customization options for password resetting are limited. The process requires additional steps and coding to make it user-friendly. While Google Firebase works well for the login page, password resetting and user verification redirect users to a separate interface, which is not very user-friendly.

I have been using the product for one and a half years. 

The solution is stable; only disruptions exist when the user does not confirm emails. 

My company has seven users. I rate the tool's scalability a seven out of ten. We had issues with scalability, particularly with configurability. Sometimes, we couldn't meet our expectations because the features provided were limited. For example, when sending customer emails, we had limited customization options.

I used open-source libraries before Google Firebase. 

The solution's deployment is easy for a front-end engineer. There are not many operations in the front end. 

I suggest reviewing the documentation and understanding the flow before starting development. It may seem complicated initially, but having a clear idea of the process will make implementation easier. Integrating one application into others becomes straightforward once you have one application set up. I rate the overall solution an eight out of ten. 

I use Google Firebase for user authentication when I work with mobile apps. Firebase is easy for other than the database, in my opinion, because it gives real-time functionalities. That's easy because if I work with raw NodeJS or Express, then when I want real-time functionalities, I have to use Socket.IO, but Firebase has its own built-in real-time capabilities, and that's easy for implementation.

The real-time database is a good feature for me. The second option is notifications. When I work with PWAs and use Firebase's functionalities, their notifications are awesome. 

The implementation is easy. The only tough part is that they have paid functionalities. So when we use any type of NodeJS or other languages, we implement Firebase, and then it's paid. But the notification service is great, and so is the real-time database.

I have used Google Firebase for a maximum of two years. If I were to review the service, it would be about paid functionalities, like implementing notifications, is easy, but debugging is not. I have to connect to my Google console and upload the functionalities every time. This doesn't make sense to me because if I want to see the console, I have to upload to it. This is the biggest reported issue from me. 

When I work in the backend with Google Firebase and implement Node.js, I have to upload the function every time. If I upload the function every time to the Google Cloud console, then sometimes it can crash. That side is disappointing for me.

I have been using it for two years. 

It is a stable product. If my client wants a real-time database, top-notch security, and easy user authentication, then we can switch to Firebase. 

Firebase's security is awesome, and implementation is easy. 

If they want a real-time database, I can easily switch to Firebase because they already have a real-time database, and the collection and structure of data is easy to understand.

Everyone on my team uses it. I have ten people on my team, and only two or three did not use Firebase early. When I told them to just read the documentation and try to implement the simple things like user authentication and storing data in the database, it was amazing because they were able to easily implement it. That's why everyone uses Firebase easily.

The documentation is very beginner-friendly. Anyone can learn the service easily.

The deployment is very easy. 

The price is too expensive.

My recommendations: 

If you want to easily implement user authentication with Google sign-in or Facebook login, you can use Firebase because it has its own functionality. You can just take their API and implement your code, then you can easily create login functionality. 

If you want to make it easy, then I suggest you use Firebase. But if you want to learn more and create custom features, then I don't suggest Firebase because it has its own built-in functions.

Learning curve:

It's easy to learn  if you want to read the documentation and research. There are two types of beginners: 

1. Those who want to research and read the documentation. For those who want to research and read the documentation, it's easy.
2. Those who just want to go to YouTube and search. And do not have any interest. 

The Firebase version is running ten point something now, but I used Firebase version eight. The functionality and the documentation are easy for me. When I want to upload an image, Firebase has the code. I copy and paste the code, change one or two things, and that's it.

Overall rating:

If I were to make a chatting application and use Firebase, I would give it a nine or nine point eight out of ten because it is easy to learn and implement. But if we consider the price, I would give it a five or four out of ten.

I use Google Firebase mainly for applications. Google Firebase has competitors like Supabase and PostgreSQL. Google Firebase has a lot of services like storage, Firestore, and push notifications. The solution also has a feature where you can change the parameters online. Other products in the market cannot compare with the many services Google Firebase provides for application development.

Also, the solution's deployment for the App Store is very easy with the swing Firebase. Mostly, 90% of people use Google Firebase because of its availability in many places. The solution is very fast, scalable, and dynamic. If you have a lot of clients, the solution will automatically scale up to the number of your clients.

Google Firebase's app testing feature for Android, where you can upload your APK, needs improvement because it's not working very well. It's not very easy because you can upload one version of your app and test it with different phones. Google needs to improve it because I tried it multiple times and found that manually testing the app works better and much faster.

Google should find a way to reduce the solution's read and write. For example, if you have a list of 100 clients for only one click, and if they read, it will be 100 reads, which is expensive. We could use a cache method, but it's still expensive. So Google should reduce the cost a bit. Like Supabase, Google Firebase can have SQL models so that we can have relational and non-relational databases at the same time. A relational database could be much cheaper in some cases.

I have been using Google Firebase since 2018.

Google Firebase is a very stable solution.

Google Firebase is a scalable solution.

Everyone uses Google Firebase because it is very easy to set up, run, and maintain. Even if you don't have a lot of experience in coding or the back end, you could deploy the solution in a very short time.

Google Firebase is an expensive solution.

Google Firebase is very fast and easy to use, but it's expensive. The solution is expensive because of the read-and-write feature. So, if you have a lot of clients and don't know how to optimize it in your app, it will cost you a lot. The solution is easy to set up, but you have to know how to read and write.

Google Firebase has a lot of services like push notifications and Firestore. For example, I once used AWS Amplify, and it's not easy to deploy. Apart from Supabase, which arrived last year in the market, Google Firebase does not have a lot of alternatives. However, the downside is that it's expensive. The solution has a special calculator, but it still is unclear how much it charges us for read and write functions.

Overall, I rate Google Firebase an eight out of ten.

I am using Google Firebase as a real-time database for all my applications. It allows me to get data in real time with an automatically refreshable website, so there is no delay. Even if the data changes, my website automatically updates, even if it is open in a browser.

Google Firebase has helped my organization by providing a real-time database, which means I don't have to worry about delays and ensures automatic website updates. It also provides an easy way to manage user authentication with various providers like Google, Microsoft, and Facebook.

The real-time database feature is the most valuable, allowing real-time feedback without needing to constantly poll the database. It enables real-time interactions similar to seeing cars moving on a map in real time.

There needs to be an easy way to duplicate a database. Currently, creating a copy of a database is a manual process, which could be improved with an option to automatically create another copy.

I have been working with Google Firebase for probably ten years.

From the point of view of reliability, Google Firebase works well with no issues.

In terms of scalability, Google Firebase handles it well. It automatically scales like YouTube when hosting video content, allowing millions of customers to stream the same content without any manual intervention.

I have not needed to contact Google support for Firebase. Whereas, I have contacted AWS support, which is really good, because I couldn't figure out certain things. For Google, I never needed the support.

Positive

I have used Google Cloud and AWS previously. Google Cloud is the cheapest and their free tier is very generous. Google Cloud has allowed me to run sites for years without any cost, unlike AWS which costs me even though it receives less traffic.

The setup process for Google Firebase is not difficult. I have looked it over and found that you don't have to know a lot to get started.

Google Cloud is the cheapest among the solutions I have used. Their free tier is very generous, allowing me to run sites with no cost.

I evaluated AWS and Azure before using Google Firebase.

I would recommend Google Firebase because it provides reliable and scalable solutions.

I'd rate the solution ten out of ten.

We use Firebase primarily for storing user data, authentication data, and many more - like Apple authentication data, Google authentication data, Facebook authentication data, and storage of any authentication data in Firestore. 

We also use it for chat modules such as one-to-one or real-time chat using the real-time database.

Firebase has been very useful to us. We have been using Firebase for three years, and it has been beneficial as we can store user data efficiently. Additionally, the access to Firestore is very easy.

Firebase provides valuable features in the Flutter framework. We can use Firebase through the SDK. The provider like Firebase gives access to their database through Stream or FutureBuilder. The integration with Flutter is seamless, making it very easy to use.

There are many features in Firebase that we have not used. As we are a small team, we have only utilized some features, however, all those features have been very useful, and there is no problem.

We have been using Firebase for three years.

Stability is excellent, given that Firebase is a Google product.

The support from Google is highly responsive. We once encountered an incident where a developer mistakenly deleted the database. We emailed Google's support team, and they promptly recovered the full database for us.

Positive

I recommend Firebase to everyone looking to use any cloud database. It is worth using and very useful.

I'd rate the solution ten out of ten.