Why Firebase services overview? - Purpose & Use Cases

The Big Idea

What if you could build a full app backend without ever touching a server?

The Scenario

Imagine you want to build a mobile app that stores user data, sends notifications, and authenticates users. Doing all this manually means setting up servers, databases, and messaging systems yourself.

You would have to write tons of code, manage servers, and handle scaling as more users join.

The Problem

Manually building and managing backend services is slow and complicated.

It's easy to make mistakes that cause downtime or data loss.

Scaling up when your app grows can be expensive and stressful.

The Solution

Firebase offers ready-to-use backend services like databases, authentication, and messaging.

It handles the hard parts for you, so you can focus on building your app.

Firebase scales automatically and keeps your app running smoothly.

Before vs After

✗ Before

Set up server, write API, manage database connections, handle user login logic

✓ After

Use Firebase Authentication, Firestore database, and Cloud Messaging with simple SDK calls

What It Enables

Firebase lets you build powerful apps faster by providing all essential backend services in one place.

Real Life Example

A startup launches a chat app using Firebase to handle user sign-in, real-time messages, and notifications without managing any servers.

Key Takeaways

Manual backend setup is complex and error-prone.

Firebase provides easy-to-use, scalable backend services.

It helps you focus on app features, not infrastructure.

Practice

1. Which Firebase service helps you manage user sign-in and identity verification easily?

easy

A. Analytics

B. Firestore

C. Authentication

D. Hosting

Solution

1. Step 1: Understand Firebase services purpose

   Authentication is designed to handle user sign-in and identity verification.

2. Step 2: Match service to function

   Firestore is for database, Hosting is for web hosting, Analytics is for tracking usage.

3. Final Answer:

   Authentication -> Option C

4. Quick Check:

   User sign-in = Authentication [OK]

Hint: User sign-in? Think Authentication service [OK]

Common Mistakes:

• Confusing Firestore with Authentication
• Thinking Hosting manages users
• Mixing Analytics with sign-in

2. Which of the following is the correct way to initialize Firebase Hosting in your project?

easy

A. firebase init hosting

B. firebase start hosting

C. firebase deploy hosting

D. firebase create hosting

Solution

1. Step 1: Recall Firebase CLI commands

   To set up Hosting, you first initialize it with firebase init hosting.

2. Step 2: Differentiate commands

   firebase deploy hosting deploys but does not initialize; others are invalid commands.

3. Final Answer:

   firebase init hosting -> Option A

4. Quick Check:

   Initialize Hosting = firebase init hosting [OK]

Hint: Init means setup, so use 'firebase init hosting' [OK]

Common Mistakes:

• Using deploy before init
• Using non-existent commands
• Confusing start with init

3. What will the following Firebase code snippet do?

const db = firebase.firestore();
db.collection('users').add({name: 'Anna', age: 25});

medium

A. Update existing user document named Anna with age 25

B. Add a new user document with name Anna and age 25 to Firestore

C. Delete user document named Anna from Firestore

D. Retrieve all users named Anna from Firestore

Solution

1. Step 1: Understand Firestore collection and add method

   The add method creates a new document in the 'users' collection with given data.

2. Step 2: Analyze code effect

   The code adds a new user with name 'Anna' and age 25; it does not update, delete, or retrieve.

3. Final Answer:

   Add a new user document with name Anna and age 25 to Firestore -> Option B

4. Quick Check:

   add() creates new document = Add a new user document with name Anna and age 25 to Firestore [OK]

Hint: add() means create new document in Firestore [OK]

Common Mistakes:

• Thinking add updates existing data
• Confusing add with get or delete
• Assuming it retrieves data

4. You tried to deploy your Firebase Hosting but got an error saying "No public directory found." What is the most likely cause?

medium

A. You did not install Firebase CLI

B. You did not create a Firestore database

C. Your internet connection is down

D. You forgot to specify the public directory during firebase init hosting

Solution

1. Step 1: Understand the error message context

   The error "No public directory found" means Firebase cannot find the folder with website files to deploy.

2. Step 2: Identify cause related to initialization

   This usually happens if you did not set or create the public directory path during firebase init hosting.

3. Final Answer:

   You forgot to specify the public directory during firebase init hosting -> Option D

4. Quick Check:

   Missing public directory = You forgot to specify the public directory during firebase init hosting [OK]

Hint: Set public directory when initializing Hosting [OK]

Common Mistakes:

• Blaming internet connection
• Confusing Firestore with Hosting
• Not installing Firebase CLI

5. You want to track how users interact with your app and also store user profiles. Which two Firebase services should you combine?

hard

A. Firestore and Analytics

B. Hosting and Cloud Functions

C. Authentication and Hosting

D. Realtime Database and Storage

Solution

1. Step 1: Identify service for storing user profiles

   Firestore is a database service suitable for storing structured user profile data.

2. Step 2: Identify service for tracking user interactions

   Analytics tracks user behavior and app usage statistics.

3. Final Answer:

   Firestore and Analytics -> Option A

4. Quick Check:

   Store profiles + track usage = Firestore + Analytics [OK]

Hint: Store data with Firestore, track with Analytics [OK]

Common Mistakes:

• Choosing Hosting for data storage
• Confusing Realtime Database with Analytics
• Mixing Storage with tracking