Firebase with React - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Firebase in simple terms?

Firebase is a service that helps you add features like databases, user login, and storage to your app without managing servers.

beginner

How does React work with Firebase?

React is a tool to build user interfaces, and Firebase provides backend services. Together, React shows data and Firebase stores or manages it.

beginner

What is the purpose of Firebase Authentication in a React app?

Firebase Authentication helps you easily add user sign-up and login features to your React app without building your own system.

intermediate

Why use Firestore with React instead of a traditional database?

Firestore updates data in real-time and works well with React’s fast interface updates, making apps feel smooth and live.

intermediate

What is a common way to connect Firebase to React components?

You usually create a Firebase config file, initialize Firebase, then use React hooks like useEffect to fetch or listen to data.

What Firebase service is used to store and sync data in real-time with React?

A Firebase Functions

B Firestore

C Firebase Analytics

D Firebase Hosting

Firestore is Firebase's real-time database service that syncs data with apps like React.

Which React hook is commonly used to fetch Firebase data when a component loads?

A useContext

B useState

C useEffect

D useReducer

useEffect runs code when components mount, perfect for fetching Firebase data.

What does Firebase Authentication provide for a React app?

A Cloud storage

B Hosting static files

C Real-time database

D User login and sign-up features

Firebase Authentication manages user sign-in and sign-up easily.

How do you initialize Firebase in a React project?

A By importing Firebase config and calling initializeApp()

B By installing React Router

C By creating a new React component

D By using useState hook

You import your Firebase config and call initializeApp() to start Firebase.

Which Firebase feature helps you store files like images in a React app?

A Firebase Storage

B Firestore

C Firebase Authentication

D Firebase Hosting

Firebase Storage is used to upload and store files such as images.

Explain how you would set up Firebase in a new React project to fetch and display data.

Think about the steps from Firebase setup to showing data in React.

Describe the benefits of using Firebase Authentication in a React app.

Focus on why Firebase Authentication saves time and effort.

Practice

1. What is the main purpose of using Firebase with React in app development?

easy

A. To replace React's state management

B. To style React components with CSS

C. To compile React code faster

D. To add backend features like database and authentication easily

Solution

1. Step 1: Understand Firebase role

   Firebase provides backend services like database and user authentication.

2. Step 2: Understand React role

   React handles the user interface and frontend logic.

3. Final Answer:

   To add backend features like database and authentication easily -> Option D

4. Quick Check:

   Firebase adds backend features [OK]

Hint: Firebase adds backend, React builds UI [OK]

Common Mistakes:

• Thinking Firebase is for styling
• Confusing Firebase with React state
• Assuming Firebase speeds up compilation

2. Which of the following is the correct way to initialize Firebase in a React app?

easy

A. import firebase from 'firebase'; firebase.init(config);

B. const app = new Firebase(config);

C. import { initializeApp } from 'firebase/app'; const app = initializeApp(config);

D. firebase.initialize(config);

Solution

1. Step 1: Check Firebase v9+ syntax

   Firebase modular SDK uses initializeApp from 'firebase/app'.

2. Step 2: Verify correct import and call

   import { initializeApp } from 'firebase/app'; const app = initializeApp(config); correctly imports and calls initializeApp with config.

3. Final Answer:

   import { initializeApp } from 'firebase/app'; const app = initializeApp(config); -> Option C

4. Quick Check:

   Use initializeApp from 'firebase/app' [OK]

Hint: Use modular import initializeApp from 'firebase/app' [OK]

Common Mistakes:

• Using old firebase namespace import
• Calling non-existent init or initialize methods
• Creating Firebase instance with new keyword

3. Given this React code snippet using Firebase Firestore:

import { useEffect, useState } from 'react';
import { getFirestore, collection, getDocs } from 'firebase/firestore';

function UsersList() {
  const [users, setUsers] = useState([]);
  useEffect(() => {
    const db = getFirestore();
    getDocs(collection(db, 'users')).then(snapshot => {
      const list = snapshot.docs.map(doc => doc.data().name);
      setUsers(list);
    });
  }, []);
  return <ul>{users.map(name => <li key={name}>{name}</li>)}</ul>;
}

What will this component display?

medium

A. A list of user names from the 'users' collection

B. An empty list because useEffect has no dependencies

C. A list of document IDs instead of names

D. A syntax error due to missing async keyword

Solution

1. Step 1: Analyze data fetching

   useEffect runs once, fetches 'users' collection documents, maps to their 'name' field.

2. Step 2: Analyze rendering

   Users state is set to list of names, rendered as list items in <ul>.

3. Final Answer:

   A list of user names from the 'users' collection -> Option A

4. Quick Check:

   Firestore docs mapped to names displayed [OK]

Hint: useEffect fetches once, maps docs to names [OK]

Common Mistakes:

• Thinking useEffect needs async keyword directly
• Confusing document IDs with data fields
• Assuming empty list due to empty dependency array

4. What is wrong with this React Firebase code snippet?

import { useEffect, useState } from 'react';
import { getFirestore, collection, getDocs } from 'firebase/firestore';

function Items() {
  const [items, setItems] = useState([]);
  useEffect(async () => {
    const db = getFirestore();
    const snapshot = await getDocs(collection(db, 'items'));
    setItems(snapshot.docs.map(doc => doc.data()));
  }, []);
  return <div>{items.length}</div>;
}

medium

A. getDocs requires a second argument for options

B. useEffect callback should not be async function

C. setItems should be called outside useEffect

D. useState initial value must be null

Solution

1. Step 1: Identify async useEffect issue

   React's useEffect callback cannot be async directly; it should call an async function inside.

2. Step 2: Confirm other parts

   getDocs usage and setItems inside useEffect are correct; initial state as empty array is valid.

3. Final Answer:

   useEffect callback should not be async function -> Option B

4. Quick Check:

   Async function inside useEffect, not async callback [OK]

Hint: Never make useEffect callback async directly [OK]

Common Mistakes:

• Making useEffect callback async directly
• Thinking getDocs needs extra arguments
• Believing setState must be outside useEffect

5. You want to build a React app that shows a live list of chat messages from Firebase Firestore. Which approach correctly updates the UI in real-time?

hard

A. Use Firestore's onSnapshot listener inside useEffect to update state on data changes

B. Call getDocs repeatedly every second inside useEffect to fetch new messages

C. Fetch messages once on component mount and never update state again

D. Use Firebase Realtime Database instead of Firestore for real-time updates

Solution

1. Step 1: Understand real-time update methods

   Firestore provides onSnapshot to listen to live data changes and update UI immediately.

2. Step 2: Compare options

   Use Firestore's onSnapshot listener inside useEffect to update state on data changes uses onSnapshot inside useEffect, which is best practice for real-time updates in React.

3. Final Answer:

   Use Firestore's onSnapshot listener inside useEffect to update state on data changes -> Option A

4. Quick Check:

   onSnapshot enables real-time UI updates [OK]

Hint: Use onSnapshot listener for live Firestore updates [OK]

Common Mistakes:

• Polling with getDocs wastes resources
• Fetching once misses updates
• Confusing Firestore with Realtime Database necessity