Why authentication identifies users in Firebase - Performance Analysis

Time Complexity: Why authentication identifies users

O(n)

Understanding Time Complexity

When a user logs in, Firebase checks their identity. We want to see how the time it takes changes as more users try to log in.

How does Firebase handle many login requests efficiently?

Scenario Under Consideration

Analyze the time complexity of the user login process using Firebase Authentication.

const email = "[e-mail]";
const password = "userPassword";

firebase.auth().signInWithEmailAndPassword(email, password)
  .then(userCredential => {
    const user = userCredential.user;
    // User is signed in
  })
  .catch(error => {
    // Handle errors
  });
    

This code signs in a user by checking their email and password with Firebase Authentication.

Identify Repeating Operations

Look at what happens each time a user tries to log in.

• Primary operation: The call to signInWithEmailAndPassword which sends credentials to Firebase servers.
• How many times: Once per login attempt, no matter how many users try to sign in.

How Execution Grows With Input

Each login request is handled separately by Firebase.

Input Size (n)	Approx. Api Calls/Operations
10	10 login calls
100	100 login calls
1000	1000 login calls

Each login is independent, so the total work grows directly with the number of users trying to sign in.

Final Time Complexity

Time Complexity: O(n)

This means the time to handle all login requests grows in a straight line as more users try to sign in.

Common Mistake

[X] Wrong: "Firebase checks all users at once, so login time stays the same no matter how many users sign in."

[OK] Correct: Each login is a separate check. More users mean more checks, so total work grows with users.

Interview Connect

Understanding how login requests scale helps you explain how cloud services handle many users smoothly. This skill shows you know how systems work under load.

Self-Check

"What if Firebase cached user credentials locally? How would that change the time complexity of login requests?"

Practice

1. What is the main purpose of authentication in Firebase?

easy

A. To store user data

B. To confirm the identity of a user

C. To speed up app loading

D. To design the app interface

Solution

1. Step 1: Understand authentication role

   Authentication is the process that confirms who a user is by checking their credentials.

2. Step 2: Differentiate from other functions

   Storing data, speeding up loading, or designing interfaces are not related to identifying users.

3. Final Answer:

   To confirm the identity of a user -> Option B

4. Quick Check:

   Authentication = Confirm identity [OK]

Hint: Authentication means checking who you are [OK]

Common Mistakes:

• Confusing authentication with data storage
• Thinking authentication speeds up apps
• Mixing authentication with design tasks

2. Which Firebase method is used to sign in a user with email and password?

easy

A. firebase.auth().signInWithEmailAndPassword()

B. firebase.auth().createUserWithEmailAndPassword()

C. firebase.auth().signOut()

D. firebase.auth().sendPasswordResetEmail()

Solution

1. Step 1: Identify sign-in method

   The method to sign in a user with email and password is signInWithEmailAndPassword().

2. Step 2: Differentiate from other methods

   createUserWithEmailAndPassword() creates a new user, signOut() logs out, and sendPasswordResetEmail() sends reset instructions.

3. Final Answer:

   firebase.auth().signInWithEmailAndPassword() -> Option A

4. Quick Check:

   Sign in = signInWithEmailAndPassword() [OK]

Hint: Sign in uses signInWithEmailAndPassword() method [OK]

Common Mistakes:

• Using createUserWithEmailAndPassword() to sign in
• Confusing signOut() with sign-in
• Mixing password reset with sign-in

3. What will the following Firebase code output if the user is not signed in?

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

medium

A. No user signed in

B. User ID: null

C. Error: user is null

D. User ID: undefined

Solution

1. Step 1: Understand onAuthStateChanged behavior

   This listener runs when the authentication state changes. If no user is signed in, the user parameter is null.

2. Step 2: Analyze the if-else condition

   If user is null (no signed-in user), the else block runs, printing 'No user signed in'.

3. Final Answer:

   No user signed in -> Option A

4. Quick Check:

   Null user triggers else message [OK]

Hint: Null user means no one signed in [OK]

Common Mistakes:

• Assuming user.uid exists when user is null
• Expecting an error instead of else message
• Confusing null with undefined

4. Identify the error in this Firebase authentication code snippet:

firebase.auth().signInWithEmailAndPassword(email, password).then(user => { console.log('Signed in:', user.uid); }).catch(error => { console.error(error.message); });

medium

A. The then callback receives a user object directly

B. The catch block should be before then

C. signInWithEmailAndPassword requires three arguments

D. The then callback receives a userCredential object, not user

Solution

1. Step 1: Check the promise return type

   signInWithEmailAndPassword returns a promise resolving to a userCredential object, not a user directly.

2. Step 2: Understand how to access user ID

   The user ID is accessed via userCredential.user.uid, so the code should use userCredential in the then callback.

3. Final Answer:

   The then callback receives a userCredential object, not user -> Option D

4. Quick Check:

   Then gets userCredential, not user [OK]

Hint: Then callback gets userCredential, access user inside it [OK]

Common Mistakes:

• Treating then argument as user directly
• Placing catch before then
• Passing wrong number of arguments

5. You want to restrict access to certain app features only to authenticated users. Which Firebase approach best identifies users to enforce this?

hard

A. Use anonymous sign-in without checking user identity

B. Store user data in Firestore without authentication

C. Use Firebase Authentication to sign in users and check their UID before access

D. Allow all users to access features without sign-in

Solution

1. Step 1: Understand access control needs

   Restricting features requires knowing who the user is, which Firebase Authentication provides by signing in users and giving unique IDs.

2. Step 2: Evaluate other options

   Storing data without authentication or allowing anonymous/no sign-in does not identify users, so access cannot be controlled securely.

3. Final Answer:

   Use Firebase Authentication to sign in users and check their UID before access -> Option C

4. Quick Check:

   Authentication + UID check = secure access control [OK]

Hint: Check user UID after sign-in to restrict access [OK]

Common Mistakes:

• Relying on data storage without authentication
• Using anonymous sign-in without identity checks
• Allowing access without sign-in