Google Firebase Reviews

I was working with Google Firebase, specifically Firestore, and also because for offline applications, that is pretty much useful for mobile, such as Android and iOS applications when we are having offline features. I am also working on the Firebase Authentication part where we can integrate it with various platforms without limits and make the authentication smaller than before.

It is simplifying user identity management, and that is fine for me.

That is pretty much useful. When we are integrating with Google Analytics and we have integrated with the site, we can see all of the things in Google Firebase, especially when it goes to WooCommerce applications. We can really analyze more information on how the sales go and what are the items which are most famous among the customers.

It helps me understand user behavior more effectively with Google Analytics.

I face difficulties with the authentication parts in Google Firebase when it goes with iOS applications. With Android applications, that is easier because Google owns it. When it goes to iOS applications, there should be a much more straightforward, smoother way. I mostly faced that with Flutter because with Flutter, there are two sides with Android and iOS. The Android part was pretty much easier for me, but when it goes to the iOS part, there was more work on that.

I have been using Google Firebase for four to five years.

In the early days, during the first years, there were some challenges during implementation, but right now they have mostly put the improvements for those, so it is making it smoother now than in the early years.

It depends on the task I am working on and the solution I am working on. Approximately how much time deployment might require is pretty much straightforward. It is either from my side or from Google Firebase side if it is getting delayed or not.

I would rate the technical support of Google an eight out of ten.

I do the installation on my own.

I work with Google Firebase. I do not utilize Firebase Cloud Messaging yet. I rate this product an eight overall.

We use the Google Firebase platform to develop mobile applications, and we use Google Firebase to have rapid prototype development for our application. It is a perfect tool to have a prototype.

There are several features that I really appreciate about Google Firebase. It has an authentication and authorization tool, a real-time database, and serverless cloud functions. I particularly value these areas of Google Firebase, and they have some FCM services for push notifications, which is excellent.

The pricing structure needs improvement since it uses cloud billing. We do not know how the pricing is calculated as it is all on the cloud. The concept that the more you use, the more you have to pay could have been much better. They could have implemented credits based on usage so that users would be able to easily calculate the pricing and provide it to customers.

I am the co-founder and CTO of the company called Aiwox (A I W O O X). We have numerous projects for mobile application development, and we have shifted from Google Firebase to Supabase because there is a fixed price for Supabase. Supabase is built on top of AWS, and it provides a very good pricing model. Some of the credits are free, and once you reach a certain limit, you know the charges.

The second improvement area is related to SQL. They provide the real-time database, which is very good, and they have gradually started including PostgreSQL, which is a relational database, but it is not production-ready yet. I may be incorrect; perhaps they have released something new, but PostgreSQL database real-time database remains a challenge with Google Firebase.

We have been using Google Firebase for more than six years.

The initial deployment and installation with Google Firebase is very easy. Compared to AWS, I would rate it five out of five for Google Firebase.

I would say that the performance is not production-ready yet. I see very few applications using Google Firebase. In our company, we have prototypes on Google Firebase and productions on AWS Cloud.

It depends on the architecture, but from the scalability point of view, I do not think it is that scalable compared to other Google Cloud services. Google also has some other cloud services, but when we compare Google Firebase, it is not as scalable.

We have not contacted technical support regarding Google Firebase. Everything is available online, and it has been there for quite some time. Community support is also excellent.

Positive

I have used AWS, Amazon Web Services, which has similar services to what Google Firebase offers.

The initial deployment and installation with Google Firebase is very easy. Compared to AWS, I would rate it five out of five for Google Firebase.

We have a team to handle this, but one person can also manage it. We had a team lead who was able to manage everything, and I have split those responsibilities among individuals.

We have a team to handle this, but one person can also manage it. We had a team lead who was able to manage everything, and I have split those responsibilities among individuals.

The pricing structure needs improvement since it uses cloud billing. We do not know how the pricing is calculated as it is all on the cloud. They could have implemented credits based on usage so that users would be able to easily calculate the pricing and provide it to customers.

We have numerous projects for mobile application development, and we have shifted from Google Firebase to Supabase because there is a fixed price for Supabase. Supabase is built on top of AWS, and it provides a very good pricing model. Some of the credits are free, and once you reach a certain limit, you know the charges.

We need some maintenance on our end because as we deploy an application to Cloud Functions, the platform may change. For example, Python 3.9 is no longer supported, so we all have to upgrade it to the latest version. Some of these challenges will be present, and we will have to have maintenance for this infrastructure. On a scale of 1-10, I rate Google Firebase an 8.

We utilized Firebase in many cases, such as volume, storage, hosting Angular and static pages, normal dynamic pages, and OAuth requirements. We also used it to create credentials for DART for our Android and Flutter applications. It is a Google-backed platform for Android applications. We have mobile applications for both Android and iOS devices, which we initially developed separately. Now, we are using Flutter for our mobile applications. We were utilizing Firebase primarily for our Android applications.

The authentication feature is good. I would rate it around eight out of ten. The process was seamless and straightforward for Gmail users. However, the authentication process was different and challenging for Microsoft accounts. While integrating it into an Angular or mobile application was easy for Google users, it was a plug-and-play. Non-Google users require additional conditions and configurations.

In terms of DevOps, such as CI/CD deployments and integrating webhooks with GitHub, GitLab, or other platforms, Firebase does not offer those capabilities at that level.

The only issue is that it is connected to GCP, not AWS or any other platform. The building process is specific to GCP. Thus, the challenge lies in directly integrating the build with GCP. 

It is very difficult to manage. When deploying code to a platform, I must indicate the target site or web subdomain to which it should be deployed. Additionally, I need to decide whether to ignore certain files or directories, such as node modules .env files, or cache related to the website. The script must be written to handle these details. While Firebase supports Next.js and React.js applications, the performance was below 65-70%, which affects scalability.

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

We need to focus more on the code level. We used GIF files and large banners, which significantly impacted loading times. Additionally, building and deploying the website has its challenges. We depend on external tools like GitHub Actions or Jenkins for the build process. This dependency is a major drawback because Firebase doesn't offer a built-in build service. Consequently, I have to handle the build process elsewhere and then deploy it to Firebase, which adds complexity.

I rate the solution's stability a five or six out of ten.

They have to work more on the DevOps part. It is improving very rapidly. We require Firebase on automation requirement. Vercel is giving that as of now.

15-18 users are using this solution.

I rate the solution’s scalability a five or six out of ten.

Since it is connected to Google through GCP, we have partnered with a channel partner for billing and support. We contacted the channel partner rather than Google directly. 

The features are good, but automation is taking a major role in every domain and category.

Firebase is cheap because bandwidth usage depends on the GCP. What we were paying for was what we were getting. If we want more features, then we have to go for another platform.

I recommend the solution based on the target audience. Suppose a company has a minimal budget for cloud platforms and offerings. In that case, Firebase might be a good option, especially if they already use Angular, as Firebase is compatible with Angular and PHP. If a company's developers are skilled in Angular and don't want to invest in React, which can be more expensive in the current market, Firebase is a suitable alternative.

Additionally, considering the growth of customer usage is essential. For example, if the number of requests has increased from 1,000 per day to 10,000 per day, the platform should be able to scale accordingly. If customer usage is relatively low, Firebase can be a cost-effective choice. However, for higher usage levels, other platforms may be more appropriate.

The performance depends on the quality of the code, how well it is optimized, the files we upload, and how we use the browser or website.

Overall, I rate the solution a four out of ten.

I use Google Firebase for user authentication when I work with mobile apps. Firebase is easy for other than the database, in my opinion, because it gives real-time functionalities. That's easy because if I work with raw NodeJS or Express, then when I want real-time functionalities, I have to use Socket.IO, but Firebase has its own built-in real-time capabilities, and that's easy for implementation.

The real-time database is a good feature for me. The second option is notifications. When I work with PWAs and use Firebase's functionalities, their notifications are awesome. 

The implementation is easy. The only tough part is that they have paid functionalities. So when we use any type of NodeJS or other languages, we implement Firebase, and then it's paid. But the notification service is great, and so is the real-time database.

I have used Google Firebase for a maximum of two years. If I were to review the service, it would be about paid functionalities, like implementing notifications, is easy, but debugging is not. I have to connect to my Google console and upload the functionalities every time. This doesn't make sense to me because if I want to see the console, I have to upload to it. This is the biggest reported issue from me. 

When I work in the backend with Google Firebase and implement Node.js, I have to upload the function every time. If I upload the function every time to the Google Cloud console, then sometimes it can crash. That side is disappointing for me.

I have been using it for two years. 

It is a stable product. If my client wants a real-time database, top-notch security, and easy user authentication, then we can switch to Firebase. 

Firebase's security is awesome, and implementation is easy. 

If they want a real-time database, I can easily switch to Firebase because they already have a real-time database, and the collection and structure of data is easy to understand.

Everyone on my team uses it. I have ten people on my team, and only two or three did not use Firebase early. When I told them to just read the documentation and try to implement the simple things like user authentication and storing data in the database, it was amazing because they were able to easily implement it. That's why everyone uses Firebase easily.

The documentation is very beginner-friendly. Anyone can learn the service easily.

The deployment is very easy. 

The price is too expensive.

My recommendations: 

If you want to easily implement user authentication with Google sign-in or Facebook login, you can use Firebase because it has its own functionality. You can just take their API and implement your code, then you can easily create login functionality. 

If you want to make it easy, then I suggest you use Firebase. But if you want to learn more and create custom features, then I don't suggest Firebase because it has its own built-in functions.

Learning curve:

It's easy to learn  if you want to read the documentation and research. There are two types of beginners: 

1. Those who want to research and read the documentation. For those who want to research and read the documentation, it's easy.
2. Those who just want to go to YouTube and search. And do not have any interest. 

The Firebase version is running ten point something now, but I used Firebase version eight. The functionality and the documentation are easy for me. When I want to upload an image, Firebase has the code. I copy and paste the code, change one or two things, and that's it.

Overall rating:

If I were to make a chatting application and use Firebase, I would give it a nine or nine point eight out of ten because it is easy to learn and implement. But if we consider the price, I would give it a five or four out of ten.

Positive

I use the solution as a database and even for Google Firebase's authentication-related stuff.

I love using Google Firebase for authentication. Anyone who develops a website or app can integrate Google Firebase's authentication part seamlessly with minimal lines of code, and it provides an API for that. Google Firebase has authentication features that are very important and necessary.

What I hate most about Google Firebase is that it has many different versions and releases new ones frequently. Once the previous version becomes outdated, all websites or apps using that version will be vulnerable and stop working. In such cases, one must upgrade the tool to another version and then make necessary changes if there are any deprecated functions. The code has to be changed or modified after an update.

I have been using Google Firebase for a year and a half. I am just a user of the solution.

It is a stable solution. Google Firebase is actively being maintained by Google. There are plenty of users of the tool, millions and millions of users. It is a completely reliable product.

Scalability is present in the tool, but at the same time, it comes with a cost.

I haven't spoken to the solution's technical support. Ten out of ten times, I have found a solution for the problem I am facing on their forum and Stack Overflow. It is simple to debug. There are plenty of times that we come across an error when someone is using the tool. The main issue in the tool is associated with its version because anytime there is a new version. There has to be many changes made. It is easy to find a solution to the challenges that one is facing.

Google Firebase has easy deployment features, and it also provides Firestore from Google Firebase, which is very helpful for deploying websites. Overall, the tool has plenty of necessary features.

The more the number of reads and writes, the more one gets charged. People can make a simple mistake since the pricing model is dynamic and based on usage, or whenever there is massive traffic to the database or anything, we get charged, and then we must pay all of the tool's charges.

People have to be very careful before choosing any cloud storage. It can get expensive pretty fast. If there is an unexpected traffic, then there will be costs.

The product provides integration features in multiple languages, such as Python, JavaScript, Golang, and all other languages. Google Firebase has documentation, which might seem a bit confusing, but one with decent knowledge can easily explore and get started with Firebase quickly.

Before jumping into any cloud infrastructure, the tool should analyze how much it would cost to run the database. Google Firebase provides a certain number of reads and writes per day, which is approximately 40,000 reads and writes. If there are more than 200 to 300 active users per day, there will be plenty of reads and writes to the database. In such a case, one can't use Google Firebase and has to upgrade to Spark, which is where it is based on usage.

The tool is fairly simple to get started with. Utilize all the features can get very complicated. One must be a pretty good developer who has a lot of experience to be able to utilize the best features. It gets really complicated over time. The basic functionality and basic usage are easy to use and easy to get started.

There are plenty of deprecated versions, and frequently upgrading them causes inconvenience.

I rate the tool a nine out of ten.

Positive

I use Google Firebase for deploying my web applications. Whenever I have leisure time, I try to code some web applications and develop them. Then, I deploy these web applications using Google Firebase.

The main part that I like about Firebase is that it provides command line tools. It gives you a set of command lines and instructions to deploy, which you can use easily to deploy in the terminal itself. There is no need to manually move the files to Firebase.

Maybe not for someone new to deployment and authentication, as it's somewhat difficult to use. You need to have some experience with deployment.

Professionally, I haven't used it, however, I've used it personally for deploying my personal projects for the past year.

I have not faced any issues with its stability.

I did not contact their support team. Whatever issues I faced, I resolved by directly searching on Google or stack overflow.

Positive

I used Dynatrace for error logging in the production environment.

There is a learning curve for about a week.

Firebase is open source and free up to a certain level, so there is no need to pay any amount up to a certain point.

We also use Google Analytics for error logging.

I can suggest Google Firebase over other deployment tools because of its seamless authentication and open-source nature.

I'd rate the solution eight out of ten.

We use Google Firebase as a platform where we can upload apps or websites, which helps in scaling them.

Google Firebase allows for seamless scaling as more people visit our website or app, helping us grow efficiently.

The connection between Firebase and the integrated development environments, especially when using Android Studio, is crucial as it saves time.

The exploration of the functions within Firebase could be improved.

I have used Google Firebase for about three years now.

Google Firebase is very stable, and I would rate its stability as a nine out of ten.

I would rate the scalability of Firebase as an eight or nine out of ten.

There is so much documentation available that I have not needed to contact customer support.

Before Google Firebase, I did not use a different solution.

The initial setup is pretty straightforward, it literally happens within ten minutes.

If you provide your app for four thousand users, the cost is around. Most of the features are free.

The cost efficiency is perfect, with many features being free. Licensing or pricing is highly cost-effective for small companies.

Oracle Apex is also a very good solution for developing apps.

I would absolutely recommend Firebase to other developers, especially those developing apps on platforms like Flutter.

I'd rate the solution seven out of ten.

We use Firebase for understanding crashes and tracking analytics about our users, which supports marketing, development, and distribution purposes.

Firebase has been helpful in providing analytics and crash insights. It still needs more detail for larger scale applications.

Crashlytics is the best feature in Firebase.

They could add a session replay to better understand how a crash or bug happened.

We have been using Firebase for maybe six or seven years.

I do not remember any major issues with stability while using Firebase.

Firebase is easy to scale.

The support team responds rapidly. There is a good community with many solutions available through shared videos on YouTube and blog posts.

Positive

I have previously worked for Huawei and Google Analytics and have experience with their customer service.

The initial setup is very easy, and the guidelines and tutorials are helpful for developers, even junior developers.

I don't know the current prices, however, it is probably average compared to others in the market.

We were considering Instana and Sentry for different business needs and have arranged meetings to decide further.

For startup or personal applications, I strongly recommend Firebase. However, for big businesses or large domains, I suggest using a different tool.

I'd rate the solution ten out of ten.