Email Sign-In Quickstart
Build a basic sign-up and sign-in screen with Firebase Authentication (email/password). Show user state on app launch and add sign-out.
Cloud / Knowledge library
Firebase
google's backend platform for apps
Why learn Firebase?
Firebase helps teams ship app backends fast without managing most server infrastructure. It provides auth, databases, hosting, serverless functions, analytics, and security tooling in one platform, which is especially useful for mobile and web apps that need real-time data and rapid iteration.
Where it came from
2011: Firebase started as a real-time database service. 2014: Google acquired Firebase. 2016: Firebase expanded into a full app development platform at Google I/O. 2017: Cloud Firestore launched as a scalable document database. 2021: Modular Web SDK (v9) became the modern import style, improving tree-shaking.
- 2011: Firebase started as a real-time database service.
- 2014: Google acquired Firebase.
- 2016: Firebase expanded into a full app development platform at Google I/O.
- 2017: Cloud Firestore launched as a scalable document database.
- 2021: Modular Web SDK (v9) became the modern import style, improving tree-shaking.
Build your understanding
Work through these exercises in order. Try the task before opening a reference.
- Build a basic sign-up and sign-in screen with Firebase Authentication (email/password). Show user state on app launch and add sign-out.
- Create a Firestore-backed task list with add, toggle complete, and live updates. Use modular SDK imports only.
- Write Firestore Security Rules so users can read/write only their own documents. Test with Emulator Suite and include one passing and one failing test case.
- Add a Cloud Function that rejects task titles shorter than 3 characters before write completion. Return a clear error to the client.
- Implement offline persistence for Firestore in a mobile app flow, then sync changes when connection returns. Display sync status to users.
More ways to practice
Realtime Task List
Create a Firestore-backed task list with add, toggle complete, and live updates. Use modular SDK imports only.
Lock Down Data with Rules
Write Firestore Security Rules so users can read/write only their own documents. Test with Emulator Suite and include one passing and one failing test case.
Serverless Validation
Add a Cloud Function that rejects task titles shorter than 3 characters before write completion. Return a clear error to the client.
Offline-First Mobile Notes
Implement offline persistence for Firestore in a mobile app flow, then sync changes when connection returns. Display sync status to users.
Documentation and sources
- Firebase Documentation (firebase.google.com)
- Get Started (Web) (firebase.google.com)
- Cloud Firestore (firebase.google.com)
- Security Rules (firebase.google.com)
- Emulator Suite (firebase.google.com)
Catalog research notes
- Web SDK v9+ modular imports are the standard for smaller web bundles.
- Cloud Firestore supports aggregation queries (count, sum, average).
- Firebase Data Connect introduced managed GraphQL over Cloud SQL (preview).
- Firebase added tighter integrations with Google Cloud and Vertex AI workflows.
Connect the ideas
Explore next
Real World Example
Real-time Inventory Sync for Boutique Retailers
Boutique retailers managing multiple pop-up locations and a centralized web storefront.
The business problem
Inventory discrepancies occur when physical sales at pop-up locations are not immediately reflected in the central database, leading to overselling of limited-edition items.
How this topic solves it
Utilizing Firebase Realtime Database to maintain a synchronized state across all client devices, ensuring that every transaction triggers an instantaneous update to the global inventory count.
- Initialize the Firebase SDK within the retail mobile application.
- Define a structured JSON node for inventory items with unique product IDs.
- Implement listeners on the client side to observe changes to specific inventory nodes.
- Execute write operations upon successful point-of-sale transactions to update stock levels.
- Configure security rules to ensure only authenticated staff can modify inventory data.
Shows how the central database acts as the single source of truth for distributed retail nodes.
Firebase Realtime JSON Tree
Mobile POS Device
E-commerce Interface
- Pop-up Client → 1:1 update stock → Central Database
- Central Database → 1:n sync state → Web Storefront
Implementation example
This code demonstrates updating a specific inventory node in the Firebase Realtime Database, which triggers an automatic sync to all connected clients.
// Reference the specific product inventory node
const inventoryRef = firebase.database().ref('inventory/item_001');
// Update stock level after a sale
inventoryRef.update({ stock: newCount });Expected business outcome
A consistent view of stock levels across all sales channels, effectively eliminating the risk of overselling during high-traffic events.
Limitations and checks
The Realtime Database uses a single JSON tree structure, which can lead to performance bottlenecks if data is not properly flattened; developers must monitor the depth of the tree to prevent inefficient data retrieval.