Firebase

As manufacturers of electronic equipment interconnected through the IoT Cloud, we needed a robust backend technology that could easily scale as our user base grew. The solution that we needed was to include a real-time database as well as the possibility of executing functions in the cloud according to that database received the data of our clients, for example, sending push notifications.

We use Firebase together with its documentary base called Firestore to execute all the transactional processes of our web app, using both its authentication and user administration system, as well as its potential as a backend for the application that we have developed in Angular and Node Js. It's one of the main reasons we went for GCP instead of AWS or Azure

We used Firebase to keep track of the attendance of students in our class. The database is relatively fast for storing attendance. It doe take a little while to set up. User authentication works well. It takes some time to set up it. One thing about the authentication that bothers us is that you can not reset the password directly. When a user creates their account, Firebase gives the user the ability to set the initial password. But afterward, Firebase only lets you reset the password by email.

We are using Firebase Authentication for backend services authentication and for users to authenticate on our app. We were facing an issue with backend services authentication.

We use Firebase as a supplemental product to Google Analytics. We have some pains around Google Analytics not being the best tool when it comes to user behavior analytics across platforms & devices. Firebase solved this issue for us and we're now able to get a holistic picture of our users engage with our product.

Firebase is used to create new native applications with a NoSQL code base. The platform allows to create any type of applications like social networks, games, news and applications like streaming video and music thanks to its video player plugin.

We use Firebase for SMS Authentication and settings management. It's great because it allows us to do that at the same time we send notifications to Android and iOS users. In like an all-in-one platform/service.

I used Firebase in a few of our projects because it supports a variety of platforms, including Android and iOS. It's also quite simple to use during the development of an application. Aside from that, Firebase has a lot of cool capabilities like real-time storage, identification, and Crashlytics, all of which can be connected to Google Analytics.

We use Firebase as a company portal for the creation, execution, authentication, and development of web and mobile applications. The implementation of the platform is fast and simple, it offers excellent functions so that the process with our applications is functional and effective. It currently integrates with more than 100 platforms, such as Slack, Google Ads, Play Store, and BigQuery, tools that we frequently use for different processes.

Firebase has been used in a lot of projects that our firm has developed, it has many great features that we use, but the most important ones are the web hosting, the authentication, and the lighting fast real-time database. This tripled allow the fast development of robust and scalable applications and web applications.

Firebase is used as a storage service in the organization. There is less time required for managing the servers. It is a managed service. It is very easy to integrate with the blackened. The user login feature uses firebase as the blackened. It is also integrated with the google cloud function service.

We use Firebase as our complete solution for authentication, analytics, testing, and monitoring for our Android, iOS, and macOS apps. We chose Firebase over all other competing solutions because of its excellent documentation, helpful community, widespread adoption, scalability, and broad platform support. Firebase enables us to use one framework for all of this across multiple platforms, devices, and languages, which has not only simplified our codebase and support footprint, but has also meant that new features and mechanisms can be rolled out more quickly across all platforms than if separate libraries and frameworks were used on each platform.

The moment you say you want to develop cross platform applications and you want a smooth implementation no matter which platform you want to deploy to, please consider FIREBASE. You see todays generation is so much obsessed with the front end part, they forget that the actual power of their application would be released when your back end support system is really backing you up. There are numerous services, and to be honest you really cant use all of them in one go.. but primarily I recommend making the start with Authentications, Databasing, CloudFunctions and Notifications. Authentications will take care of all the extra code you have previously written with how to manage users- from signing in to changing passwords. Databasing is highly efficient with the realtime Db especially when you want to listen to changes that happen to your data in realtime. The Clound FUnctions is your step towards serverless architecture, when all you have to do is keep functions to do with your project ready to fire on the cloud... rather than maintaining an entire server! And if you have a mobile user base, you have to see how easy it is to send notifications via firebase

It's being used by the customer success team, data, and engineering team. We are able to track all of the data that is stored from our system/app.

Firebase provides one bucket solution for all platforms. We have connected firebase for the last two years by using it for mobile application development, real-time database, [and to] engage services for our whole organization. It uses a great authentication mechanism without any interpretation. The best thing about the user's feedback [is that] they are very satisfied with a very seamless and smooth experience. They provided very detailed documentation that helps a person code with basic skills also.

Our mobile team is currently using Firebase Analytics, Crashlytics and very recently expanding our usage to include RemoteConfig. <br><br>With the RemoteConfig, we are using to configure feature flags remotely. The online console is very intuitive and the SDK is easy to implement. This address the problem of being able to toggle on/off features remotely without having to make a new release.<br><br>Likely for Crashlytics and Analytics, we find the SDK incredibly easy to use and with plenty of public resources/tutorials available. <br>

The technical and marketing department is using Firebase. The technical department is using it for users authentication, no-SQL database, remote configuration, push notifications, and crash log. Marketing team use the analytics dashboard to get the insights into our product

We used Firebase for handling our mobile push notifications. It was our platform for both sending push notifications and measuring the success of those pushes. It was used mostly by the content team, producers specifically. That was the one group that sent pushes. Our analytics folks used the platform as well. It gave us a solution for sending push notifications and measuring the impact of our pushes.

It's mainly being used by our Product, UA, and Developer Teams. The Product Team uses it to A/B test push notifications and the subscription trial period. UA team mainly uses to track users across various events as well as Google UAC campaigns. The Developer team mainly uses the crashlytics to troubleshoot and fix stability issues. This allows them to help prioritize their task better based on their priority.

It's being used mainly by our analytics and mobile teams. We were forced to migrate from Google Analytics, which is bad from an analytics standpoint (because Firebase has an inferior interface and is more restrictive in terms of tracking App interactions) but good from a mobile diagnostics point of view (because it has better diagnostics than Google Analytics).

It helps us understand Mobile App Version adoption, as well as gauge the success of new feature rollout and/or experience changes.

Firebase is being used by multiple departments across the organization, namely Technology, Product, Marketing, Analytics, etc. While the Tech team uses this for monitoring crashes and performance, the product team uses this for user funnel and user behavior analysis. The marketing team uses this for AB testing, in-app messaging, push notification, etc. Analytics uses this for creating dashboards and pulling user analytics.

I am using Firebase as a realtime database and backend as a service for a prototype real estate application I am building. I first used Firebase while I was attending a coding boot camp: we used it for one of our big projects. There are a number of advantages to using this.

Firebase was a great choice for us to build our apps. Since it provides Mobile Backend as a Service it helps us to save our time. For our project, we needed a remote database in the cloud. After comparing most of the cloud solutions, finally, we decided to go with firebase because of its good with overall performance, great documentation and, of course, its a product by the Google brand. It was easy to use and just needed basic coding skills. It is powerful enough to make you satisfied.

We use Firebase to provide push notification services for mobile applications and some internal business tools. For us, it is used to provide push services to internal employees, and to provide push services to end users of our mobile applications. We find it to be simple to use, effortless to maintain, and effective at its job.

Firebase is one and only tool for all of the mobile backends, especially Android. Most of the times when creating mobile applications in the Android studio it is recommended to use Firebase. We use Firebase for JSON data pushing and parsing from Firebase bucket. We use it every place possible, for web apps, smartphone apps, push notifications and many authorization protocols.