Google Firebase Reviews

We're primarily using the solution for developing SaaS expert system software. I wanted to host it with Google so users can subscribe and then develop online from anywhere. That way my software can run on their server.

The Firebase hosting and the automated authentication service, as well as the cloud functionality, are the solution's most valuable features. 

The documentation and guides for implementation are very good.

The user interface is very good and easy to navigate. 

The solution is easy to upload and overall easy to use.

The cold start-up of the cloud function needs to speed up. For me personally, I'm not experienced in anything there, however, I've just read online it's a problem.

I've been using the solution for two months.

I have a lot of confidence in Google because it's a pretty large enterprise and we have been using Google products for a long time. I don't have any fear of failed stability; I have full confidence in their products.

I'm the only one using and testing the solution right now. I'm using it on a daily basis.

I haven't needed technical support and therefore have never contacted them.

I used Jelastic but the pricing was poor. I switched to Google because it is free up to a certain point.

The initial setup is straightforward and very simple. To deploy the solution takes less than an hour.

I simply used the online documentation and step-by-step guide to handle the implementation myself.

The solution is free up to a certain point. You don't have to add your credit card until you exceed the limits allowed.

I did evaluate other options, including Amazon AWS, but I had difficulty. I'd subscribe using my credit card and they'd deduct my money but I would not get any codes to authenticate. After a long time, I was frustrated so I moved to Google.

I'm using the latest online version of the solution, which is public cloud-based.

I can develop the solution offline if I like. I go offline to develop the solution and then I'll go online again to test because testing online wastes my time. I do the test of my software offline, but when I want to use the cloud to test I'll jump online. 

I'd rate the solution ten out of ten.

We use Firebase on-premise. Our primary use cases are for push notifications and for realtime chat.

I'm really happy with the performance and with what it gives us. 

The most valuable feature I like is that it is in realtime. Updates are also very fast. 

We use Firebase for media processing and we are growing more. As we grow, the pricing goes up and it's high compared to competitors. The solution is expensive. 

In the next release, they should focus more on realtime features. 

It's stable. Stability and the performance are really good.

We have plans to expand it across the organization. 

I never had to contact their technical support. 

Licensing costs are on a monthly basis. 

I would rate it a seven and a half out of ten. Not a ten because I haven't explored every facet to it. I am very happy with what I have seen so far. 

We use Firebase as a proof of concept to introduce Apogee functionality in the future. We need to simulate some scenarios using Apogee as a lesson for API management and Firebase is the backend database we use to simulate custom scenarios regarding the customer needs.

We use the public cloud version.

I found the flexibility of handling and dealing with the database through EDL to be very useful.

Their technical support needs to be enhanced with more support for customers.

They should also improve the monitoring and control for the database to monitor the performance and fine-tuning of the database itself. Automatic detection of potential errors or failures in the database would also be very helpful. For example, I would like to receive notifications for the admin to take appropriate action for database failures.

Deployment and maintenance requires two or three people for us.

I think it's a rich community, but they should increase the line support of technical issues and get official support to users or customers for Firebase so they can get their answers quickly. Most questions can be answered from the history of other questions and there is a community for all these questions and answers, which helps newcomers to with deployment and maintenance of the Firebase Database.

I was mainly using Oracle Database, which has different concepts for different scenarios, to some extent. Since it's one year old, it's tough to move to the Firebase Database.

I have had a good experience in both Google and Oracle environments and I also have had good experiences in Google constantly, which is a cloud environment, in which you can build a private cloud environment.

The initial setup was straightforward. It took around two or three hours.

I would rate Firebase as eight out of 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.

The primary use case is the documentation.

Firebase is awesome and easy to use. It is a database without any schema from the client-side. Additionally, it has security rules to control database read/write operations in real-time.

• Information stored in the cloud and readily available everywhere.
• The big power of their the data host.

Firebase uses JSON, and the storage format is very different to that of SQL. This does not allow for easy migrations.

The support team is responsive and well-informed.

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.