Google Firebase Reviews

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.

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.

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.

We use Google Firebase for the database in the backend. We also use some of the Firebase functions for the website to interact with. We host two apps on it. One is an Ionic app that connects to the Google Play Store and the Apple Play store. The other one also has a Firebase backend, Firebase functions, and some schedule functions to make some payments.

What I like most about Google Firebase is that it's one of the easier options to host a website or app quickly. I think the backend integration is quite quick with the Firebase.

I think the migration into a data warehouse, or Google BigQuery, should be a bit more automated. There are still some manual hiccups, and it wasn't as user friendly as some of the other components.

I would like to see faster data migration and some support for other languages in the next release. Google Firebase has functions, but it'll help to do a .NET Core kind of function or a bit of additional support for other languages. Right now, I feel like it's very Google-centric.

I have been using Google Firebase for about 18 months.

Google Firebase is definitely a stable solution.

Google Firebase felt like it was scalable to a point with our solution. But when we went a bit further with our databases, we ran into some problems.

We had a concept where we were white labeling and had different speeds. As soon as we connected six different apps to the same backend, we started having problems. Then we had to split into duplicate databases, and that wasn't perfect.

I also found that we hadn't used the real-time database in the BI component, and we used the Firestore component. Originally, we had a real-time database, and we migrated to the Google Cloud Firestore database. I found that I could easily migrate that into Google BigQuery. But there's a couple of steps. First, you have to do the backup, and then you have to import these backups into Google BigQuery.

I did that about six months ago and was slightly annoyed that there were no streaming functions. Scheduling the import was very difficult with Firestore. We had to use a couple of other tools to create schedulers to import. But the import on the Google BigQuery and the Firestore component was still a manual process, which was a bit annoying.

Google Firebase is quick to set up and relatively easy to install. But it depends on the context, dependent on the growth of the application. For example, if you have a site that's already developed, doing the hosting and configurations, with authentication plugins and more, will probably take anywhere from a couple of days to a week.

Google Firebase was set up by myself and one of the other developers.

The pricing component is a bit confusing when it comes to what exactly you'll pay for, but I wouldn't say it's expensive. I just found it a bit confusing to understand what exactly it was saying. There aren't any extra payments for the license. 

We started with Firebase, but we recently considered moving over to Azure. But the benefits we would've received weren't worth the migration effort.

I would recommend Google Firebase for startups and people specifically focusing on apps.

Based on our use case, I would give Google Firebase an eight.

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.

I started using it for web development, taking advantage of the SDK to speed up the development process. Since you do not need to create an API, you can connect to Firebase from JavaScript.

The product that we sell has a lot of important features, and one is the real-time chat that was only made possible by Firebase. Currently, we are working on a migration from another document database to Firestore, which is the second generation of Firebase.

Firestore makes possible more things than Firebase. It is a mix of Datastore and Firebase. We needed a database that provides high consistency and scalability, given the real-time feature. This helped our organization a lot because the process to develop everything was very fast, thanks to its SDK.

The Realtime Database feature is the most important for us since we are able to see changes in the database the moment they are happening. So, we built a real-time chat where users are able to talk with each other. Also, the push notifications on smartphones are another important feature that we discovered later, and it made a big impact on our portal.

The Firebase functions that act as triggers to let you know when there are changes in the database are very helpful.

Another important feature would be the SDK. You do not have to create an API since you are able to query the database directly from JavaScript or any other language.

I would like to have a facility for testing possible scenarios by writing dummy data and then doing different queries. This would help me to better develop applications.

I have been using Google Firebase for two years.

We have never had problems in the two years that we have been working on this database.

We currently have around 500,000 and the database works very well.

So far, we haven't need to contact customer service. The documentation is clear about how to implement it.

We were using CouchDB and we changed because we needed to use a managed service. The one available on GCP was Firebase.

The initial setup is simple since you only need to create an account on the Firebase website.

We implemented this completely using our internal team.

The monthly cost is based on writing data and queries to the database. The price, I would say, is cheap. You can use this database in the free tier even for production with small applications.

We did not evaluate other solutions.

Queries to the database were very simple. However, modeling is a challenge and I recommend running proof of concepts when you want to store something new in the database.

Overall, I have to say that this database is great.

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