Firebase with Next.js - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Firebase in the context of web development?

Firebase is a platform by Google that provides backend services like database, authentication, and hosting to help build web and mobile apps quickly without managing servers.

beginner

How does Next.js help when using Firebase?

Next.js is a React framework that supports server-side rendering and static site generation, which helps improve performance and SEO when building apps that use Firebase services.

beginner

What is the purpose of initializing Firebase in a Next.js app?

Initializing Firebase sets up the connection between your Next.js app and Firebase services, allowing your app to use features like authentication, database, and storage.

intermediate

Why should Firebase initialization code be written to run only once in Next.js?

Because Next.js can reload modules during development and run code on both server and client, initializing Firebase only once prevents errors and duplicate connections.

intermediate

What is a common way to protect Firebase API keys in a Next.js app?

Firebase API keys are safe to expose because they are not secret, but sensitive operations should be done in server-side code or Firebase security rules to protect data.

What Firebase service is commonly used for user login in a Next.js app?

A Firebase Realtime Database

B Firebase Authentication

C Firebase Storage

D Firebase Hosting

Firebase Authentication provides easy-to-use methods for user login and identity management.

Where should Firebase initialization code be placed in a Next.js project?

A In a separate module that runs once and is imported where needed

B Inside every React component directly

C Only in the _app.js file without modularization

D In the public folder as a static file

Placing initialization in a separate module ensures Firebase is initialized once and reused safely.

Which Next.js feature helps improve SEO when using Firebase data?

A Static file hosting

B Client-side rendering only

C API routes disabled

D Server-side rendering (SSR)

SSR allows pages to be pre-rendered on the server with Firebase data, improving SEO.

Is it safe to expose Firebase API keys in a Next.js frontend app?

A Yes, because they are not secret keys

B No, they must be hidden always

C Only if encrypted

D Only in development mode

Firebase API keys identify your project but do not grant admin access, so they are safe to expose.

What is a recommended way to secure Firebase data access in a Next.js app?

A Disable authentication

B Hide API keys in client code

C Use Firebase security rules and server-side code for sensitive operations

D Store data only in local storage

Firebase security rules and server-side logic protect data access properly.

Explain how to set up Firebase in a Next.js app from initialization to using authentication.

Think about the steps from project creation to login feature.

Describe best practices for using Firebase API keys and securing data in a Next.js application.

Focus on what is safe to expose and how to protect data.

Practice

1. What is the main purpose of integrating Firebase with a Next.js application?

easy

A. To add backend features like database and user authentication easily

B. To replace Next.js routing with Firebase functions

C. To convert Next.js into a mobile app framework

D. To remove the need for React components in Next.js

Solution

1. Step 1: Understand Firebase role

   Firebase provides backend services such as database and authentication that can be added to frontend apps.

2. Step 2: Understand Next.js role

   Next.js is a frontend framework for React apps, which can use Firebase to add backend features.

3. Final Answer:

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

4. Quick Check:

   Firebase adds backend features to Next.js apps = C [OK]

Hint: Firebase adds backend features to frontend apps [OK]

Common Mistakes:

• Thinking Firebase replaces Next.js routing
• Confusing Firebase with mobile app frameworks
• Assuming Firebase removes React components

2. Which of the following is the correct way to initialize Firebase in a Next.js project?

easy

A. import { initializeApp } from 'firebase/app'; const app = initializeApp(firebaseConfig);

B. const app = new Firebase(firebaseConfig);

C. firebase.initialize(firebaseConfig);

D. import firebase from 'firebase'; firebase.init(firebaseConfig);

Solution

1. Step 1: Check Firebase v9+ syntax

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

2. Step 2: Verify correct usage

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

3. Final Answer:

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

4. Quick Check:

   Use initializeApp from 'firebase/app' = B [OK]

Hint: Use modular import and initializeApp for Firebase v9+ [OK]

Common Mistakes:

• Using old Firebase namespace syntax
• Calling non-existent methods like firebase.init
• Creating Firebase instance with 'new' keyword

3. Given this Next.js Firebase code snippet, what will be logged if the user is not signed in?

import { getAuth, onAuthStateChanged } from 'firebase/auth';
const auth = getAuth();
onAuthStateChanged(auth, user => {
  if (user) {
    console.log('User ID:', user.uid);
  } else {
    console.log('No user signed in');
  }
});

medium

A. Error: user is null

B. User ID: undefined

C. No user signed in

D. Nothing will be logged

Solution

1. Step 1: Understand onAuthStateChanged behavior

   This function triggers callback with user object if signed in, or null if not.

2. Step 2: Analyze code branches

   If user is null (not signed in), else branch logs 'No user signed in'.

3. Final Answer:

   No user signed in -> Option C

4. Quick Check:

   Null user triggers else branch = A [OK]

Hint: Null user means else branch runs [OK]

Common Mistakes:

• Assuming user object is always defined
• Expecting an error when user is null
• Thinking nothing logs if no user

4. You wrote this code to fetch data from Firestore in Next.js but get an error:

import { getFirestore, collection, getDocs } from 'firebase/firestore';
const db = getFirestore();
async function fetchData() {
  const querySnapshot = await getDocs(collection(db, 'users'));
  querySnapshot.forEach(doc => {
    console.log(doc.data());
  });
}
fetchData();

What is the most likely cause of the error?

medium

A. doc.data() is not a function

B. The collection name 'users' is invalid

C. getDocs does not support async/await

D. Firebase app was not initialized before calling getFirestore()

Solution

1. Step 1: Check Firebase initialization requirement

   Firestore requires Firebase app to be initialized before calling getFirestore().

2. Step 2: Analyze other options

   'users' is valid collection name; getDocs supports async/await; doc.data() is valid method.

3. Final Answer:

   Firebase app was not initialized before calling getFirestore() -> Option D

4. Quick Check:

   Initialize Firebase app before Firestore = D [OK]

Hint: Always initialize Firebase app before Firestore calls [OK]

Common Mistakes:

• Skipping Firebase initialization
• Misunderstanding async/await with getDocs
• Assuming collection names cause errors

5. You want to secure a Next.js page so only authenticated users can access it using Firebase Auth. Which approach is best?

hard

A. Check user authentication only in getStaticProps and serve static content

B. Use Firebase Admin SDK on server side to verify user token in getServerSideProps

C. Use Firebase Auth on client side and redirect unauthenticated users to login page

D. Store user password in cookies and check it manually in the page component

Solution

1. Step 1: Understand authentication in Next.js

   Client-side checks can be bypassed; server-side verification is more secure.

2. Step 2: Use Firebase Admin SDK in getServerSideProps

   This allows verifying user tokens securely on server before rendering page.

3. Step 3: Analyze other options

   getStaticProps runs at build time, not per request; storing passwords in cookies is insecure.

4. Final Answer:

   Use Firebase Admin SDK on server side to verify user token in getServerSideProps -> Option B

5. Quick Check:

   Server-side token verification = A [OK]

Hint: Verify user token server-side with Firebase Admin SDK [OK]

Common Mistakes:

• Relying only on client-side auth checks
• Using getStaticProps for auth checks
• Storing passwords insecurely in cookies