Google Firebase Reviews

Google Fire is providing a lot of features, such as the deployment of our application, and the real-time database where we can store data.

Google Firebase has helped our organization internally because we can deploy the applications and store data in the databases.

The most valuable feature of Google Firebase authentication and deployment.

I have been using Google Firebase for approximately five years.

Google Firebase is scalable.

The scalability of Google Firebase is good.

We have approximately 10 to 12 developers who use the solution as per the requirements of the projects. We plan to increase usage in the future.

I rate the support from Google Firebase a four out of five.

Positive

I have not used a similar solution to Google Firebase.

The setup of Google Firebase is straightforward.

I have received a return on investment using Google Firebase.

I rate the price of Google Firebase a four out of five.

I did not evaluate other solutions.

We have one person that does the maintenance of the solution.

I would recommend this solution to others.

I rate Google Firebase a nine out of 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 use the solution for authentication and faster backend deployment of applications.

The solution has a comprehensive framework with well-integrated features, including authentication, database, scalability, etc.

The solution's pricing could be better.

It is a very stable solution.

It is a very scalable solution.

The solution's initial setup process has a medium complexity.

It is an expensive tool. Also, the additional cost depends on the use cases.

I rate the solution a nine out of ten. It provides faster backend deployment for applications. Although, it could make your applications dependent on the technology.

I'm using Google Firebase for Backend as a Service, while in the front end, I'm using AppGyver. The major use case for Google Firebase is that it's a backend server for mobile applications.

The most beautiful feature of Google Firebase is that it gives you a lot of functionalities out of the box, without you having to develop or having to complete a solution. For example, identity management is integrated, and security is out of the box, particularly security for the user and the ability of each user to see his data.

I also like that Google Firebase has a really good performance and is comparable to MongoDB. It's on the same level, and sometimes, it's on an even higher level than MongoDB.

Other functions that Google Firebase has that I find valuable include information dissemination, mail automation, and SMS, available out of the box.

Another valuable feature of the solution is that it allows you to develop some functionalities on the server side, so you can write JavaScript functions on the server side and use those functions quite easily. Google Firebase gives you almost a full backend environment out of the box without you having to do any deployments or a lot of administration because all administration is given out of the box.

There's always room for improvement in every product, and the major improvement that's needed in Google Firebase is its simplification, particularly for unsavvy users or non-technical users. If you're not tech-savvy, it would be very difficult for you to use the functions of the solution and understand its security rules.

If you want even non-technical people to find it easy to use Google Firebase, it should be simplified because the difference between screen-derived management and code-derived management isn't complex, so simplification wouldn't be an issue.

Another area for improvement in the solution is the functionality of querying a database, for example, the database in my company is DocumentDB, but Google Firebase doesn't support SQL queries, and using SQL language will dramatically increase usage. Each database has its language for querying, and I like SQL which is a standard query language. It's really difficult to query databases because, on each database, you have to learn a different language, so in DocumentDB and some other databases, there's a layer that gives you the ability to query with regular SQL language, but Google Firebase doesn't have that layer or functionality.

An additional feature I'd like to see in the next version of the solution is better querying. Another feature I'd like added to Google Firebase is for the security to be derived by screens, rather than by code, meaning that it can be automated by screens, and not by coding, then you can take it out of the development area, so it can be maintained by non-tech savvy users.

I've been using Google Firebase for almost one year now.

Google Firebase is stable and is significantly more stable than other solutions, for example, MongoDB. Per my usage of the solution at a start-up level, I haven't experienced any problems with it in terms of stability, but I've read that some customers complain about it.

Google Firebase is a scalable solution.

I never needed to contact Google Firebase technical support because I could manage any issue myself as the documentation for the solution was self-explanatory.

I reviewed and compared Google Firebase against different Backend as a Service, or backend solutions for mobile devices, such as Backendless and Xano. There's also MongoDB which is a huge database, but it's on a different level and focuses. Eventually, I chose to go with Google Firebase because of its functionality and cost. The solution was cheaper than the others, so it was better in terms of cost and functionality.

Google Firebase is SaaS and cloud-based, so it's really easy and straightforward to set up, even if you don't have that much knowledge about it.

Pricing for Google Firebase is not so expensive, and if you're a start-up with a small amount of data, it will be quite cheap, and there's even a free tier that you can use. If you're doing a pilot with a reasonable amount of data, for example, just a few gigabytes, it's still on the free tier. If you increase the amount of data, Google Firebase pricing is still reasonable.

The solution has two levels of pricing: the no-cost and the pay-as-you-go. The no-cost pricing level means that if you do AB testing, analytics, app distribution, app indexing, authentication, and storage on the free tier, you can do ten thousand authentications a month for free. For ten thousand email authentications or mobile authentications, it's also free. For fifty thousand identification management and identity checks, it's free. One gigabyte of storage is free, and ten gigabytes for networking is also free. Twenty thousand documents a day is free.

For pay-as-you-go, it's one cent per authentication if you are in the United States. If you are outside of the United States, it will cost you six cents per authentication. For storage after one gigabyte, it'll be ten cents per additional gigabyte, for example, two gigabytes amount to ten cents, three gigabytes would cost twenty cents, and so on.

I evaluated AppGyver, and I'm using it together with Google Firebase. I also evaluated Backendless, Xano, and MongoDB.

I'm using the cloud version of Google Firebase, so it's just one version and it's always the latest version.

Three developers, myself included, use Google Firebase. As the solution is SaaS, most of the heavy maintenance is handled by Google, but it's my team who handles the application administration and maintenance.

My advice for users of DocumentDB and Google Firebase is to first make sure that DocumentDB is the right solution because, at the start, DocumentDB would be good enough, but as you're growing your applications, you'll realize that DocumentDB isn't the only solution, or isn't the right solution for you. This means that the cost of ownership becomes much, much bigger, so my first advice is to focus on the type of database and figure out what's the best database for you, whether it's a relational database or another type. As soon as you get your answer, you'll find that Google Firebase has a very wide range of solutions it can support.

My rating for Google Firebase is nine out of ten because it's a good solution and it's maintained by Google, and Google has invested enough in it.

I'm a Google Firebase user.

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 use Google Firebase to monitor mobile applications.

The most valuable feature of the solution stems from the fact that its messaging system is very good. Firebase Crashlytics is also very good.

In Google Firebase, reporting is an area with shortcomings where improvements are required to be made in the future. Sometimes, it's not easy to retrieve data based on the pre-defined reports. There are some things you would like to measure, and it gets really hard to gather from the reports in Google Firebase, so there is a need to make available a custom report.

I have been using Google Firebase for four to five years. I am just a customer of the solution.

It is a stable solution.

It is a very scalable solution.

Plenty of people in my organization use Google Firebase.

The solution's technical support is good. I rate the technical support an eight out of ten.

Positive

The initial setup of the product is easy.

The product can be installed in a few hours.

The solution is deployed on the cloud.

Though I can take care of the installation phase of the product by myself, it is usually taken care of by a developer.

In terms of price, Google Firebase can be described as a cheap product. My company makes monthly payments towards the licensing costs attached to the solution. There are no additional costs apart from the licensing costs attached to the solution.

My company chose Google Firebase since it is one of the most popular tools in the market that is easy to use, making it the best product.

Google Firebase is easy to maintain, and only one person is required to maintain it.

If someone is looking for a scalable and cheap solution, I would suggest they use Google Firebase.

I rate the overall tool a nine out of ten.

We use Google Firebase for static hosting and identity connection for applications.

The product’s most valuable features are integration and hosting.

The platform's bandwidth is quite expensive. Its price could be better.

We have been using Google Firebase for a few years.

The product has good stability.

It is a scalable product. We have around 100 Google Firebase users in our organization and, further, we plan to increase the usage.

The technical support services are excellent.

The initial setup process is good. It takes approximately an hour to complete and requires three executives for maintenance.

We implement the solution with the help of our in-house team.

Google Firebase’s pricing needs improvement.

I rate Google Firebase a nine out of ten. I recommend it for enterprise businesses.

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.