Google Firebase Reviews

We already use this technology in our company to build our Android and iOS mobile applications and to communicate with our back-end infrastructure.

Google Cloud Functions: Allows us to create functions without any infrastructure apart from the Google App Engine. These functions can have several kinds of triggers:

• Realtime Database Triggers
• Firebase Authentication Triggers
• Firebase Analytics Triggers
• Cloud Storage Triggers
• Cloud Pub/Sub Triggers
• HTTP Triggers

Google Cloud Auth: Allows our Android and iOS mobile applications and JavaScript codes to make authentication with almost no effort. The reason is because the Auth has already implemented it for us.

Google Cloud Real-time Database: Allows our Android and iOS mobile applications and JavaScript codes to record and retrieve data with persistence and minimum effort.

In my humble opinion, Google Cloud Functions (which is still a BETA version) needs to have more control over the uploaded functions. That is, it needs more options for controlling the functions itself. I might think about some characteristics that can improve a lot this:

- A START button to start the function. This button should be
incorporated in each one of the functions that the developer created and
deployed in Google Cloud Functions;
- A STOP button to stop the function. This button should be incorporated
in each one of the functions that the developer created and
deployed in Google Cloud Functions;
- A RESTART button following the save behavior as above buttons with
RESTART capability.
- A better and improved log view. The actual LOG view has a Slow
performance to show the log items and also it doesn't allow fast searching
for past log items. For example, whenever we need to look for a block of
log items that happened in the past, it's very difficult to access that
block of code.
- Capability to save the log to an external tool.

I did not find any stability issues yet.

Our actual phase in development (MVP), doesn't allow me to give my opinion on this point.

Currently, it has not been necessary to contact technical support, due to the vast and informative documentation with Google Standard.

We tried to use the AWS cloud. They have a very good solution, although the documentation is a little verbose, in my humble opinion.

The setup is very easy and straightforward. You just need to follow the documentation from the Google App Engine.

They have a free tier that will cover most projects. For more intensive use, you pay as you use it, but the price is very cheap.

We evaluated Amazon AWS, but due to the reasons explained above, especially the flowery documentation, we decided to go through Google App Engine and Google Firebase. We have no regrets at all.

I would say that they should go ahead with Google App Engine and Google Firebase.

The most valuable features of Google Firebase have been Analytics, Remote Config, and Crashlytics. Additionally, a lot of companies have used push notifications which is important. There is little maintenance required.

Google Firebase could improve the ability to create our own reports, other than what's available on the dashboard. For example, if we want to customize the report or export the data, this is a large task. 

Crashlytics was not very helpful, it doesn't give enough information to narrow down the problem.

I have been using Google Firebase for approximately one and a half years.

Google Firebase is stable and we don't have any performance issues.

The scalability of Google Firebase is good, but there are some limitations. For example, once you are set up, there's no way you can delete the data or change the settings. It's durable, handles many loads, and pushes the data when the user is not aware.

I have not used technical support.

The setup of Google Firebase was an easy process.

We are using the free version of Google Firebase.

Google Firebase is a very good solution.

I rate Google Firebase an eight out of ten.

Our primary use case is with a chatbot and file usage. Let us say you wanted to pay for your utility bill and your data at the same time. We do this using a reward commodity known as cash tokens. This includes checking your wallet's balance and topping it up.

One of the challenges I was facing when I was using it was the library called Google Dialogflow which allows you to connect your chatbot with an intent. So there is so much adding when you are trying to connect it with your service because you have to do a lot of repetition writing a new intent, putting it step by step so it is good to escape. I believe it should be flexible and dedicate the intents based on the relating and to write a lesser code when doing that.

I have been using Google Firebase for the past two years.

When it comes to stability I had an issue during training with downtime, I do not know maybe because of more traffic on the chatbot.

The scalability is good.

There is plenty of documentation available. I think there is plenty of group support available and Google support as well. The website has plenty of information.

The price is perfect and very clearly defined. The price during the trial setup is free and then you move to a paid service.

I would rate Google Firebase a ten out of ten.

We use the solution for user management.

The solution is useful for managing users and user authentication.

We had some compatibility issues with Elixir. It had some library compatibility issues. We did a workaround through Google Cloud Functions and achieved the desired output.

I have been using the solution for the last four years.

I rate the tool’s stability a ten out of ten.

I rate the tool’s scalability a ten out of ten. In the past, we had 70,000 users. The usage was reduced later.

The initial setup is simple. The solution is cloud-based.

I rate the pricing a five out of ten.

Overall, I rate the tool a ten out of ten.

Firebase has multiple uses. My team uses it for the mobile app, while the audit team uses Firebase for the web app. We are also using Firebase to handle notifications into the mobile and web app.

I love Firebase's notifications, crash analytics, and bug tracking. It gives you detailed reporting about app usage and users.

Firebase's real-time information isn't technically real-time. It takes a while to upload user activity into the app. It's not as fast as Datadog, the other solution we use. 

I've been using Firebase for two years at my current company, but they were using it before I was hired. 

Firebase is stable.

I believe Firebase is scalable. 

Firebase was already set up when I started, but I know that the integration steps are explained well in detailed documentation.

I rate Google Firebase eight out of 10. Firebase is a good product. The free version is decent, so you can start with that and pay for more features as your needs grow. I think it's a fantastic product to start with.

Google Firebase is one I like a lot because it gives us a little bit more power and accessibility when it comes to publishing apps a lot quicker and for the needs that we have.

The documentation for Google Firebase is great. Also, what I like about it is the integration to Android, which is the reason I went with Firebase. Android is the biggest mobile platform out there currently, bigger than IOS, especially in South Africa.

The only thing that I won't do on Firebase is the hosting side of things for a progressive web app because it feels like you actually still need to download the app first before you can actually get into the functionality of the app.

So, it's not really a website, but it's web-based, and the app needs to be like a downloadable app. In that sense, I'm using normal Linux hosting and PHP for normal websites. I still have to split my software into a web app. If there's something that needs to be improved, it is that if you publish an app as web-based that you don't have to physically download the app or that the app doesn't download in the background. 

I would rather not publish as a progressive web app. Initially, on first opening up, the app seems very slow. After that it's quick, but it feels like the app needs to be downloaded first before you can actually get into the functionality of the app.

I've been using it for about six or seven months.

In the case of your first setup, if you're not sure what you want to do, it can become a bit of a problem. If you've done something wrong, it's very difficult to get rid of your project. There are some unique IDs that are left behind. So, the initial stages were a little bit difficult in that sense because if you make a mistake, you can't reuse what you have done.

However, once I got used to working with Firebase, it was nice and easy. Firebase is a Google product, but in the beginning, it didn't seem like one. Google is making a lot of changes, which makes us developers make other changes a lot as well.

The moment you go into volumes, then you work on a pay-per-volume basis.

I would recommend it if you're experimenting and starting off because of the way Google gives you a lot of free options when the project is still small. However, if you're thinking of a big project where there's going to be costs and a lot of traffic, then I would recommend that you decide on Firebase, Azure, or AWS from the beginning before you actually do something. For the experimental side, Firebase is fantastic.

If you're going to do mobile apps and need to publish to play store and have functionalities such as push notifications, analytics, AdMob, and monetization, then Firebase definitely is the way to go.

I would rate Google Firsebase at eight on a scale from one to ten.

The primary use case for this solution is the backend for the mobile app.

We tried to save costs by cutting some unnecessary operational things in the infrastructure and in the backend.

The main feature for us is that the tools are all in one place and that you don't have to bother with the backend system and the infrastructure.

As we were not able to calculate the amount of traffic and the bandwidth, we were not able to calculate the pricing accurately. There was no way of knowing how the rise in traffic would impact the price.

While we used this solution, it was quite stable and it worked. We have had five people trying and working with this platform.

We haven't tested the scalability performance of this platform. We did not do any stress or any other load tests. Although I have not tested this myself, I have read that there are some problems with the scalability.

We did not have a need to contact the technical support.

We are using Mircosoft Azure in parallel with Google Firebase.

The initial setup was easy to install and it is easy to use, very friendly. 

We implemented ourselves. We did not use any third party.

It is not easy to calculate the cost per copy, use or if the load rose dramatically we did not know how that would impact the final price.

The pricing for the authentication is based on SMS rates and is not consistent all over the world. For example, the cost in the US and Canada is one cent, but six cents in Serbia and the rest of the world. This should be adjusted. 

We did evaluate other options, including AWS, and one more platform based in Python. 

It's a good product for prototyping, with a nice interface and is easy to work with, but difficult to predict the cost.

I would rate this solution a seven out of ten.

We use the platform to deploy our software projects.

The product is complicated for beginners to understand. 

I have been using Google Firebase for around two and a half years.

We have around 50 Google Firebase users in our organization. 

The architecture and higher management decided to set up all the projects on Firebase, which is why we are using it.

We need to install Firebase from the terminal and set up everything before deploying it, whereas some other tools require less setup.

I would not recommend the product to others and rate it a six out of ten.