What advice do you have for others considering Google Firebase?

I have deployed one project in the cloud. I have used some services of the solution for other use cases. The services similar to notification services, Google Analytics, and Crashlytics are not easy to use in other tools. I will recommend the solution if someone wants to use the notification services, Messaging, Analytics, and Crashlytics. However, I will not suggest if someone wants to use Firebase Cloud Storage. The solution is difficult to learn if someone is just starting their career. If we get a little bit of guidance from a senior, it will be very easy. I number the patchwork for app versioning and deployment just like Android versioning. The first digit will be for batches from right to left, the second for major updates, and the third for a complete app version change. I increase the number by one for every build, patch it, and publish it. I use the same logic if I am deploying in Firebase. Most of the applications I have worked on are e-commerce-based applications. The main requirement for clients in such applications is conversion rate. When a user interacts with a particular product, the client wants to know whether the user purchased the product or not. They want to know where the users lost interest and went away without making the payment. Google Analytics helped me fix such issues much better than any other product. I'm very happy with it. Sometimes, I couldn't figure out how to fix issues when working on iOS. Suppose I’m just upgrading Firebase through workspace.yaml, sometimes, I may need to check whether the native version is supported. I will have to go through the documentation again. It will be much better if it is fixed by changing the version in workspace.yaml. Everything else works well. Overall, I rate the solution an eight out of ten.

I use the solution for real-time data synchronization of applications. I use the tool to build native applications using React Native Firebase. Google Firebase integrates well with React Native Firebase. Google Firebase has me. It has a large online community, and it offers most of the features one would need to build an application. Setting up Google Firebase for user authentication and management is quite straightforward and easy. Tracking user engagement is possible with Google Firebase since it easily integrates with Google Analytics, and it is also easy to set it up inside applications. My company also uses Crashlytics, which is included in Google Firebase and is sometimes handy and useful. There is nothing specific about how Firebase Cloud Messaging improves the way my company interacts with product users. My company uses the product since it easily fits into the stack of tools we use. The users don't feel anything about what our company does on the back end, and it also doesn't affect them. Although my company has not experienced any bugs or crashes in production, we have tested the tool well enough. Once or twice, when there were crashes, reports from Firebase Crashlytics helped debug or pinpoint the location where the problem was and the reason why the problem arose. Google Firebase has affected our company's uptime and scalability part since it has had a surprising impact on our development time. With the tool, my company is able to rapidly create prototype applications and roll them out for users for feedback, based on which we can make changes to improve the product. The product helps my company to rapidly build prototypes for our projects and get inputs from our customers. I rate the tool a ten out of ten.

We use Google Analytics for marketing purposes. Overall, I rate the tool an eight out of ten.

Overall, I rate the product a nine out of ten.

Overall, I rate the tool a ten out of ten.

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.

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

I recommend the solution to those who plan to use it. I rate the overall solution a six and a half out of ten.

Google Firebase is very fast and easy to use, but it's expensive. The solution is expensive because of the read-and-write feature. So, if you have a lot of clients and don't know how to optimize it in your app, it will cost you a lot. The solution is easy to set up, but you have to know how to read and write. Google Firebase has a lot of services like push notifications and Firestore. For example, I once used AWS Amplify, and it's not easy to deploy. Apart from Supabase, which arrived last year in the market, Google Firebase does not have a lot of alternatives. However, the downside is that it's expensive. The solution has a special calculator, but it still is unclear how much it charges us for read and write functions. Overall, I rate Google Firebase an eight out of ten.

I am using the latest version of Google Firebase. Overall, I rate Google Firebase an eight out of ten.

I rate the solution an eight.

I'm an end-user. I am using the latest version of the solution. I highly recommend the solution to anyone who wants to start working in the cloud. The time to market is very short, and the ease of use is great. It offers great resources. I'd rate the solution nine out of ten overall.

I would rate Google Firebase a ten out of ten.

You can use some of Google's services and it's okay. The functionality, the authentication, and the notifications of Firebase are really good, so it's what I strongly recommend people to use, however, the database the real-time functionality is not good. I'd rate the solution seven out of ten.

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.

You can use this solution for lightweight use but I would not recommend being dependant on it. When you want to scale, you will need to have your own server, services and infrastructure. I would rate this solution a six out of ten.

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.

Google Firebase is a very good solution. I rate Google Firebase an eight out of ten.

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.

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.

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.

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.

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.

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.

I would rate Firebase as eight out of ten.

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.