Why User profile data in Firebase? - Purpose & Use Cases

The Big Idea

What if your app could update user profiles instantly and securely without any manual work?

The Scenario

Imagine you run a small website where users sign up and share their info. You keep all their details in a simple spreadsheet or text file. Every time someone updates their profile, you have to manually find their row and change the data.

The Problem

This manual way is slow and risky. You might overwrite the wrong data or miss updates. As more users join, it becomes impossible to keep track without mistakes. Plus, you can't easily control who sees what info or keep data safe.

The Solution

Using Firebase to store user profile data means all updates happen automatically and safely in the cloud. Firebase handles saving, updating, and syncing data instantly across devices. It also keeps data secure and lets you control access easily.

Before vs After

✗ Before

Open spreadsheet -> Find user row -> Edit fields -> Save file

✓ After

firebase.database().ref('users/' + userId).set({name: 'Alice', age: 30});

What It Enables

You can build apps where user profiles update live, stay secure, and scale effortlessly as your community grows.

Real Life Example

A social app where users update their profile pictures and info anytime, and friends see changes immediately without refreshing.

Key Takeaways

Manual profile data handling is slow and error-prone.

Firebase automates and secures user data storage and updates.

This enables real-time, scalable, and safe user profile management.

Practice

1. What is the main purpose of storing user profile data in Firebase Firestore?

easy

A. To host static website files

B. To run server-side scripts automatically

C. To send emails to users

D. To save personal information for each user securely

Solution

1. Step 1: Understand user profile data purpose

   User profile data holds personal details like name and email for each user.

2. Step 2: Identify Firebase Firestore role

   Firestore stores this data securely and allows easy access and updates.

3. Final Answer:

   To save personal information for each user securely -> Option D

4. Quick Check:

   User profile data = personal info storage [OK]

Hint: User profiles store personal info, not run scripts or host files [OK]

Common Mistakes:

• Confusing Firestore with hosting or email services
• Thinking Firestore runs backend code automatically
• Assuming user profiles are for sending emails

2. Which Firebase Firestore syntax correctly creates a document for a user profile with ID 'user123'?

easy

A. db.collection('users').doc('user123').set({name: 'Alice'})

B. db.users('user123').add({name: 'Alice'})

C. db.collection('users').add('user123', {name: 'Alice'})

D. db.doc('users/user123').create({name: 'Alice'})

Solution

1. Step 1: Review Firestore document creation syntax

   Use collection('name').doc('id').set(data) to create or overwrite a document.

2. Step 2: Match syntax with options

   db.collection('users').doc('user123').set({name: 'Alice'}) matches correct syntax: collection, doc, then set with data object.

3. Final Answer:

   db.collection('users').doc('user123').set({name: 'Alice'}) -> Option A

4. Quick Check:

   Correct Firestore doc creation = db.collection('users').doc('user123').set({name: 'Alice'}) [OK]

Hint: Use collection().doc().set() to create user profile docs [OK]

Common Mistakes:

• Using add() with document ID specified
• Wrong method names like create() instead of set()
• Incorrect chaining of methods

3. Given this code snippet, what will be the output if the user document does not exist?

const docRef = db.collection('users').doc('user999');
docRef.get().then(doc => {
  if (doc.exists) {
    console.log(doc.data().name);
  } else {
    console.log('No user found');
  }
});

medium

A. No user found

B. undefined

C. Error: Document not found

D. null

Solution

1. Step 1: Understand doc.exists property

   doc.exists is false if document does not exist in Firestore.

2. Step 2: Follow code logic for missing document

   If doc.exists is false, code logs 'No user found'.

3. Final Answer:

   No user found -> Option A

4. Quick Check:

   Missing doc triggers else block = 'No user found' [OK]

Hint: Check doc.exists before accessing data to avoid errors [OK]

Common Mistakes:

• Assuming doc.data() returns null or undefined
• Expecting an error instead of else block output
• Ignoring the else condition

4. Identify the error in this Firebase Firestore code to update a user's profile name:

db.collection('users').doc('user123').update({
  username: 'Bob'
});

medium

A. update() cannot be used to change existing fields

B. Missing await or then to handle promise

C. Field name should be 'name' not 'username'

D. Document ID 'user123' must be a number

Solution

1. Step 1: Check Firestore update method usage

   update() returns a promise and should be handled with await or then.

2. Step 2: Identify missing promise handling

   Code does not handle promise, which can cause silent failures.

3. Final Answer:

   Missing await or then to handle promise -> Option B

4. Quick Check:

   Firestore update returns promise, must handle it [OK]

Hint: Always handle promises with await or then in Firestore calls [OK]

Common Mistakes:

• Thinking update() cannot change fields
• Assuming field names must be fixed
• Believing document IDs must be numeric

5. You want to store user profiles with optional phone numbers. Which Firestore data structure best handles missing phone numbers without errors?

hard

A. Set phone number field to empty string if missing

B. Always set phone number field to null

C. Include phone number field only if user provides it

D. Create a separate collection for phone numbers

Solution

1. Step 1: Understand optional fields in Firestore

   Firestore allows documents to omit fields that are not provided.

2. Step 2: Choose best practice for optional data

   Including the phone number field only when available avoids storing empty or null values and reduces confusion.

3. Final Answer:

   Include phone number field only if user provides it -> Option C

4. Quick Check:

   Omit optional fields if missing to keep data clean [OK]

Hint: Omit optional fields instead of storing empty or null values [OK]

Common Mistakes:

• Storing empty strings which can confuse queries
• Using null values that may cause unexpected behavior
• Overcomplicating with separate collections for simple optional data