Offline persistence in Firebase - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is offline persistence in Firebase?

Offline persistence allows your app to save data locally on the device so it can work without an internet connection and sync changes when back online.

beginner

How do you enable offline persistence in Firebase Firestore for a web app?

You enable it by calling firebase.firestore().enablePersistence() before using Firestore.

beginner

What happens to data changes made while offline in Firebase?

Changes are saved locally and automatically synced to the server when the device reconnects to the internet.

intermediate

Name one limitation of Firebase offline persistence.

Offline persistence has limited storage size and may not support complex queries while offline.

beginner

Why is offline persistence important for mobile apps?

It improves user experience by allowing the app to work smoothly without internet and prevents data loss during connection drops.

How do you enable offline persistence in Firebase Firestore for a web app?

A Set offline: true in config

B Call firebase.firestore().enablePersistence()

C Use firebase.database().goOffline()

D No action needed; it's automatic

You must explicitly call enablePersistence() to turn on offline support in Firestore web apps.

What happens to data written while offline in Firebase Firestore?

A It is saved locally and synced later

B It is sent to the server immediately

C It is lost until connection returns

D It causes an error

Firestore saves offline writes locally and syncs them automatically when online.

Which Firebase product supports offline persistence by default on mobile?

A Firebase Hosting

B Firebase Authentication

C Firebase Firestore

D Firebase Cloud Functions

Firestore supports offline persistence by default on Android and iOS.

What is a common limitation of offline persistence in Firebase?

A No local data storage

B Requires manual sync

C No syncing when online

D Limited local storage size

Offline persistence has limited storage capacity on the device.

Why is offline persistence useful for users?

A It allows app use without internet

B It speeds up internet connection

C It disables data syncing

D It deletes old data

Offline persistence lets users keep using the app even without internet.

Explain how Firebase offline persistence works and why it is useful.

Think about how apps keep working without internet and then update later.

Describe how to enable offline persistence in Firebase Firestore and mention one limitation.

Focus on setup steps and what might not work well offline.

Practice

1. What is the main purpose of enabling offline persistence in Firebase Firestore?

easy

A. To speed up internet connection

B. To save data locally so the app works without internet

C. To encrypt data on the server

D. To backup data to another cloud service

Solution

1. Step 1: Understand offline persistence concept

   Offline persistence allows the app to store data locally on the device.

2. Step 2: Identify the benefit

   This local storage lets the app work even when there is no internet connection.

3. Final Answer:

   To save data locally so the app works without internet -> Option B

4. Quick Check:

   Offline persistence = local data storage for offline use [OK]

Hint: Offline persistence means local data storage for offline use [OK]

Common Mistakes:

• Thinking it speeds up internet
• Confusing with data encryption
• Assuming it backs up to another cloud

2. Which Firebase Firestore method correctly enables offline persistence in a web app?

easy

A. firebase.firestore().enablePersistence()

B. firebase.firestore().startPersistence()

C. firebase.firestore().enableOffline()

D. firebase.firestore().activatePersistence()

Solution

1. Step 1: Recall the official method name

   The correct method to enable offline persistence is enablePersistence().

2. Step 2: Check other options

   Other options like startPersistence(), enableOffline(), and activatePersistence() are not valid Firebase Firestore methods.

3. Final Answer:

   firebase.firestore().enablePersistence() -> Option A

4. Quick Check:

   Enable persistence method = enablePersistence() [OK]

Hint: Use enablePersistence() to turn on offline support [OK]

Common Mistakes:

• Using incorrect method names
• Confusing with other Firebase services
• Missing parentheses after method

3. Consider this code snippet in a Firebase web app:

firebase.firestore().enablePersistence()
  .catch((err) => {
    if (err.code == 'failed-precondition') {
      console.log('Multiple tabs open');
    } else if (err.code == 'unimplemented') {
      console.log('Persistence not supported');
    }
  });

console.log('Persistence enabled');

What will be printed if the browser does not support offline persistence?

medium

A. Persistence not supported

B. Multiple tabs open

C. Persistence enabled

D. No output

Solution

1. Step 1: Understand error handling in enablePersistence()

   If the browser does not support offline persistence, the error code is 'unimplemented'.

2. Step 2: Identify the console output for 'unimplemented'

   The catch block logs 'Persistence not supported' for this error code.

3. Final Answer:

   Persistence not supported -> Option A

4. Quick Check:

   Unsupported browser error = 'unimplemented' message [OK]

Hint: Check error code 'unimplemented' for unsupported browsers [OK]

Common Mistakes:

• Ignoring error codes
• Assuming persistence always enables
• Confusing 'failed-precondition' with unsupported

4. You wrote this code to enable offline persistence:

firebase.firestore().enablePersistence();
firebase.firestore().enablePersistence();

But your app throws an error about multiple tabs. What is the problem?

medium

A. You need to call enableIndexedDbPersistence() instead

B. You forgot to import Firebase

C. Persistence is not supported in your browser

D. Calling enablePersistence() twice causes a conflict

Solution

1. Step 1: Analyze multiple calls to enablePersistence()

   Calling enablePersistence() more than once can cause a 'failed-precondition' error due to multiple tabs or instances.

2. Step 2: Understand error cause

   This error means only one tab can have persistence enabled at a time, so calling it twice in the same app causes conflict.

3. Final Answer:

   Calling enablePersistence() twice causes a conflict -> Option D

4. Quick Check:

   Multiple enablePersistence() calls = conflict error [OK]

Hint: Call enablePersistence() only once per app instance [OK]

Common Mistakes:

• Ignoring multiple calls cause errors
• Assuming import errors cause this
• Confusing with browser support issues

5. You want to enable offline persistence in a Firebase web app that may open in multiple tabs. Which approach correctly handles this scenario?

hard

A. Use enableIndexedDbPersistence() and catch 'failed-precondition' error to fallback to enableMultiTabIndexedDbPersistence()

B. Call enablePersistence() twice to ensure all tabs have persistence

C. Use enableMultiTabIndexedDbPersistence() and catch 'failed-precondition' error to fallback to enablePersistence()

D. Disable persistence and rely only on online data fetching

Solution

1. Step 1: Understand multi-tab persistence support

   Firebase provides enableMultiTabIndexedDbPersistence() to allow persistence across multiple tabs.

2. Step 2: Handle errors properly

   If multi-tab persistence fails with 'failed-precondition', fallback to single-tab enablePersistence() to avoid errors.

3. Final Answer:

   Use enableMultiTabIndexedDbPersistence() and catch 'failed-precondition' error to fallback to enablePersistence() -> Option C

4. Quick Check:

   Multi-tab persistence = enableMultiTabIndexedDbPersistence() with fallback [OK]

Hint: Use multi-tab persistence with fallback to single-tab [OK]

Common Mistakes:

• Calling enablePersistence() multiple times
• Ignoring multi-tab persistence errors
• Disabling persistence unnecessarily