Google Firebase Reviews

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.

We primarily use the platform to manage our apps. For example, in one instance, we get data from the Australian government regarding the cost of fuel via an API. Then we store the data in Firestore and then we use it in our app, according to the state and according to the cities to show the price of fuel within them.

The processing time has been drastically reduced. We have it down to a few minutes from 45 minutes. It's made everything so much faster.

Using the batch, it takes mere minutes to update the server. Normally, if we have a task, such as 12,000 records to be updated, it used to take 45 minutes to update. Now, after changing the code to a batch query it takes around one minute or less than one minute to update the records to Firestore.

If there's data added to the solution, there's a good record of it so it's easy to track everything.

Everything is updated automatically, which is very helpful.

The solution has a lot of features related to notifications and analytics. You can see information about how many users are on the app and from which country they are using the app.

Earlier I was using Firebase, however, now I am using Firestore. Firestore is much better than Firebase as it is the advanced version of Firebase and also it reduces the developer's time even more. It provides for queries. In Firebase you don't have that many queries to implement, get, or sort data. Firestore provides a lot of queries including MySQL. We find it much better. Firebase should offer some more of the features that exist in Firestore.

The solution needs to offer capabilities to work offline. Like Firestore, we should be able to do insertion, updating, and deletion offline. 

When we connect to the internet, it should automatically update data to the server.

I've been using the solution for the last two years.

The solution is very stable and very reliable. There aren't bugs or glitches. They have a Crashlytic feature as well, where you can see on which line of code the app has crashed if you need to. It's very transparent.

The solution is scalable and easy to use. As a developer, when I'm working on it, I know what I want out of my database. We can add the APIs and WAP services that we use with ease. We can build both a front end and back end with it. It's also fast. It can be used for both apps and web development as well. It's flexible.

We have five people at our organization that use it. There are two developers on iOS and two on Android and then we have a developer for the backend tool.

The solution offers very good documentation of everything. They also provide demos regarding the Firestore or Firebase or any feature you want to implement. It's not very tough to use anything due to the proper documentation. Therefore, we don't really need to reach out to technical support to do any troubleshooting.

We currently use Firestore and we like it much better due to the fact that you can work offline and there are many excellent features that just aren't available in Firebase.

We previously used Back4App. It has similar functionality to Firebase. We switched, however, due to the fact that Firebase is easy to handle and they have great documentation available. 

I'm also still actually using Back4App, however, I don't find that great. I found Firebase easier in comparison to Back4App. There just isn't the same level of documentation. I really have to search for information. 

Also, unlike Firebase, you have to buy a plan for it, no matter the number of users whereas Firebase is free for the first few users.

The solution is not complex. It's very straightforward. It is very easy to import or add. It is a very easy process.

During the first week, we arranged pre-requisites on the Firebase console. We added a package name, and an app name and updated the server file. After that, we downloaded it and add it to our project then ran the project. Everything is automatic. There are also files that we added and are updated. 

The deployment is very fast. It is about five minutes in total. It depends upon the internet speed, of course. Initially, we had to run the app on our device.

We have one or two people that handle maintenance.

A developer has to maintain the upgrades of the libraries and Cadency versions. Whenever we add any feature or something, or if then we have to upgrade the version for different dependencies, we'll have to do some maintenance. The maintenance part involves looking for cracks in the apps. 

Right now, we're using the free version. The solution allows for a specific number of users that can use it for free. Then, then the plan can be upgraded according to the number of users, or according to the storage that we need on Firebase. Pricing, therefore, depends upon the client or the number of users coming to the app.

Typically, we start with the free option, and if we need to, we'll ask the client to upgrade the plan.

Under the free plan, they offer authentication, and have a Firestore Cloud Function, hosting, and a real-time database as well as storage, therefore you do get a lot of things included and you don't have to pay for any of it until you add too many users or need more storage.

I'd advise users actually go to Firestore instead of Firebase, as there are just a lot more features that you have access to.

Overall, I would rate the solution eight out of ten. If it offered the same features as Firestore, I'd rate it higher.

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'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 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.

Google Firebase helps us build and run applications.

The solution could improve by providing an improved SDK tool and automatic indexing for databases.

I have been using Google Firebase for approximately four years.

The solution is stable.

Google Firebase is scalable.

The price of Google Firebase is very good.

I would recommend this solution to others.

I rate Google Firebase a nine 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. 

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.