// our stack - Firebase
Firebase, the natural backend for mobile.
Firebase is a Backend-as-a-Service (BaaS) platform from Google that bundles everything you need to build a mobile or web application: real-time database, authentication, serverless functions, file storage and push notifications. No server to manage, no infrastructure to provision. It's the backend we choose for FlutterFlow mobile projects - including on client projects such as Giphar.
Let's discuss your Firebase project// what Firebase covers
A complete ecosystem, hosted by Google.
Firebase isn't a single tool: it's a suite of services you activate à la carte depending on your project's needs. Each one is hosted, scaled and maintained by Google.
Cloud Firestore - document database
Firebase's primary database. A flexible document/collection model, real-time listeners that propagate changes to all connected clients, and Security Rules to secure access from the frontend. The free plan includes 50,000 reads and 20,000 writes per day.
Authentication - user management
Email/password, Google, Apple, Facebook, GitHub, phone (OTP) - Firebase Authentication handles the full flows without you having to build them. JWT tokens are integrated with Firestore Security Rules for unified access control.
Cloud Functions - serverless logic
Node.js or Python functions triggered by Firebase events (Firestore write, new sign-up, HTTP call) or a schedule. Ideal for processing that shouldn't run on the client side: sending emails, business validation, syncing to other systems.
Realtime Database - live synchronisation
Firestore's predecessor, still relevant for ultra-simple, very low-latency synchronisation cases (chat, presence indicators, live scores). For any new project, Firestore is recommended - Realtime Database remains an option for very specific needs.
Cloud Storage - files and media
Upload files (images, videos, PDFs) directly from the mobile or web client, with Security Rules that control who can read or write. It integrates natively with Firestore to store metadata and with Cloud Functions to process uploaded files.
Firebase Cloud Messaging (FCM) - push notifications
Send push notifications on iOS, Android and web without dedicated infrastructure. FCM is the market standard for mobile notifications - used by a large share of consumer mobile applications. Send quotas are unlimited.
// when Firebase is relevant
The situations where Firebase is clearly the right choice.
Mobile application with FlutterFlow
Firebase is FlutterFlow's native backend. Authentication, Firestore, Cloud Storage, FCM: everything integrates in a few clicks in the FlutterFlow interface, with no integration code to write. It's the combination we deploy for iOS/Android mobile projects that need to ship fast.
Real-time synchronisation
Messaging, order statuses updated live, collaborative dashboards, presence indicators - Firestore propagates changes to all connected clients without polling. This is the feature where Firebase is hard to beat in terms of implementation simplicity.
Fast MVP and prototype
No server to configure, no infrastructure to provision: Firebase lets you start a project in a few hours. For a mobile MVP where time to market matters more than the sophistication of the data model, it's a rational choice.
Authentication with social providers
Google, Apple, Facebook, phone (OTP) login - Firebase Authentication handles these flows without any server-side development. For a consumer application that needs to offer several login methods, it's a significant time saving.
// concrete examples
What we deploy with Firebase.
- 01
Business mobile application (FlutterFlow + Firebase)
Field staff use an iOS/Android app to capture data in real time: visits, inspections, forms. Firebase syncs the data to Firestore, triggers Cloud Functions for notifications and processing, and stores the photos taken in Cloud Storage.
- 02
Built-in chat or messaging
A communication channel between users of an application - between a customer and an advisor, between members of a field team. Firestore handles real-time message synchronisation, FCM sends the push notifications on mobile.
- 03
Authentication for a WeWeb app
Firebase Authentication can serve as an identity provider for a WeWeb application, particularly when the project already includes a Firebase backend or requires social login (Google, Apple). Firebase tokens are passed to the backend APIs to validate requests.
- 04
Automation via Cloud Functions
Automatic triggering of processing on an event: a new Firestore record triggers a Cloud Function that sends a confirmation email, calls a third-party API, or syncs to another system. Comparable to what n8n does for more complex orchestrations.
// limits to know
What Firebase doesn't do well - and our recommendation.
NoSQL and data modelling
Firestore is a document database. Complex relational queries (joins, aggregations, cross-filters across several collections) are difficult to write and expensive in reads. If your data model is heavily relational, Xano (PostgreSQL) will be far better suited.
Costs at scale
The free plan is generous to get started, but the pay-as-you-go model can hold surprises at scale. Poorly optimised data modelling (excessive Firestore reads) or badly written Cloud Functions can make the bill climb fast. An audit of the structure before going to production is recommended.
Dependence on the Google ecosystem
Vendor lock-in is more pronounced with Firebase than with Xano. The data lives in Google's infrastructure, exporting requires effort, and Firestore's Security Rules are specific to the platform. For projects with data sovereignty or European hosting requirements, other options are worth considering.
// our recommendation
We use Firebase mainly on FlutterFlow mobile projects - it's the natural and most productive integration. For web applications with complex business logic, we favour Xano + WeWeb. The two stacks can coexist: Firebase for mobile, Xano for web. See our case studies and projects to see these choices in context.
// F.A.Q
Frequently asked questions about Firebase
What is Firebase and what is it used for?
Firebase is a Backend-as-a-Service (BaaS) platform from Google. It bundles a set of hosted cloud services - real-time database, authentication, serverless functions, file storage, hosting, push notifications - that developers consume directly from the client (mobile or web) without managing a server. Firebase is particularly used for mobile applications (Flutter, React Native, iOS, Android) and web applications that require real-time synchronisation.
What is the difference between Firestore and Realtime Database?
Firestore (Cloud Firestore) is the successor to Realtime Database. It offers a more structured document/collection data model, more powerful queries, better scalability and more predictable performance. Realtime Database is still relevant for very simple, low-latency synchronisation cases. For any new project, Firestore is recommended by default.
Is Firebase suitable as a mobile app backend with FlutterFlow?
Yes, Firebase is FlutterFlow's native backend. The integration is native and frictionless: authentication, Firestore, Cloud Storage, Cloud Functions - everything is configured directly in the FlutterFlow interface. This is the combination we use at ezacae for mobile projects that need to ship to production fast.
Is Firebase free?
Firebase offers a free plan (Spark) with generous quotas to get started: 1 GB of Firestore storage, 50,000 reads and 20,000 writes per day, 10 GB of outbound transfer per month. Beyond that, the Blaze plan (pay-as-you-go) bills by usage. The absence of a fixed cost is convenient for MVPs, but costs can climb on a high-volume production application if the data modelling and Security Rules are not optimised.
What are the limitations of Firebase compared to Xano?
Firebase is a NoSQL database (documents/collections). This simplifies getting started, but makes complex relational queries difficult and expensive. Xano is built on PostgreSQL, which enables joins, aggregations and rigorous relational modelling. Cloud Functions is powerful but harder to debug and maintain than a Xano backend with its visual workflows. Vendor lock-in is also more pronounced with Firebase: the data lives in Google's infrastructure.
Is Firebase suitable for a web application (WeWeb)?
WeWeb can connect to Firebase via REST APIs or the JavaScript SDK. It's a valid option if you already have an existing Firebase backend. For the new web projects we build, we recommend Xano as the backend instead, for its relational modelling and more maintainable business logic. Firebase remains our choice for mobile projects with FlutterFlow.
// see other tools
A Firebase project? Let's get moving.
Let's discuss your needs and see how Firebase can serve your mobile or real-time project.
Let's talk!no-commitment chat · quick reply