FCM setup in Firebase - Time & Space Complexity

Time Complexity: FCM setup

O(n)

Understanding Time Complexity

When setting up Firebase Cloud Messaging (FCM), it's important to understand how the time to complete setup tasks grows as you add more devices or messages.

We want to know how the number of operations changes as the system scales.

Scenario Under Consideration

Analyze the time complexity of the following FCM setup steps.

// Initialize Firebase app
const app = initializeApp(firebaseConfig);

// Get messaging instance
const messaging = getMessaging(app);

// Request permission and get token
const token = await getToken(messaging, { vapidKey: 'YOUR_VAPID_KEY' });

// Listen for messages
onMessage(messaging, (payload) => {
  console.log('Message received: ', payload);
});
    

This sequence sets up FCM by initializing, requesting permission, getting a device token, and listening for messages.

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

• Primary operation: Requesting a token for each device using getToken.
• How many times: Once per device or client app instance.

How Execution Grows With Input

Each new device requires a separate token request, so the number of token requests grows directly with the number of devices.

Input Size (n devices)	Approx. API Calls/Operations
10	10 token requests
100	100 token requests
1000	1000 token requests

Pattern observation: The number of token requests grows linearly as devices increase.

Final Time Complexity

Time Complexity: O(n)

This means the time to complete setup tasks grows directly in proportion to the number of devices.

Common Mistake

[X] Wrong: "Getting a token once will cover all devices automatically."

[OK] Correct: Each device or app instance must request its own token, so one token cannot serve multiple devices.

Interview Connect

Understanding how setup operations scale helps you design systems that handle many devices efficiently and shows you can think about real-world cloud service behavior.

Self-Check

"What if we batch token requests for multiple devices at once? How would the time complexity change?"

Practice

1. What is the main purpose of Firebase Cloud Messaging (FCM)?

easy

A. To host web applications

B. To store user data securely in the cloud

C. To create user authentication systems

D. To send notifications and messages to users' devices

Solution

1. Step 1: Understand FCM's role

   FCM is designed to send notifications and messages to devices.

2. Step 2: Compare with other Firebase features

   Other options describe different Firebase services, not FCM.

3. Final Answer:

   To send notifications and messages to users' devices -> Option D

4. Quick Check:

   FCM = Messaging service [OK]

Hint: FCM = Firebase messaging to devices [OK]

Common Mistakes:

• Confusing FCM with data storage
• Thinking FCM handles authentication
• Assuming FCM hosts websites

2. Which Firebase method is used to request permission for notifications in a web app?

easy

A. Notification.requestPermission()

B. firebase.messaging().getToken()

C. firebase.initializeApp()

D. firebase.auth().signIn()

Solution

1. Step 1: Identify permission request method

   Web notifications require calling Notification.requestPermission() to ask user consent.

2. Step 2: Differentiate from other Firebase methods

   getToken() retrieves the token after permission; initializeApp() sets up Firebase; signIn() is for authentication.

3. Final Answer:

   Notification.requestPermission() -> Option A

4. Quick Check:

   Permission request = Notification.requestPermission() [OK]

Hint: Permission uses browser Notification API, not Firebase method [OK]

Common Mistakes:

• Using getToken() to request permission
• Confusing initializeApp() with permission request
• Thinking signIn() handles notifications

3. Given this code snippet, what will console.log(token) output if permission is granted and token is retrieved successfully?

const messaging = firebase.messaging();
Notification.requestPermission().then(() => {
  return messaging.getToken();
}).then(token => {
  console.log(token);
}).catch(err => {
  console.error('Error:', err);
});

medium

A. undefined

B. A string token representing the device registration

C. An error message

D. null

Solution

1. Step 1: Analyze permission and token retrieval

   If permission is granted, messaging.getToken() returns a string token.

2. Step 2: Understand console.log output

   console.log(token) prints the token string, not undefined or null.

3. Final Answer:

   A string token representing the device registration -> Option B

4. Quick Check:

   Successful getToken() = string token [OK]

Hint: getToken() returns string token on success [OK]

Common Mistakes:

• Expecting undefined or null instead of token
• Assuming error logs on success
• Confusing token with permission status

4. You wrote this code to get an FCM token but always get an error. What is the likely mistake?

const messaging = firebase.messaging();
const token = messaging.getToken();
console.log(token);

medium

A. Missing permission request before calling getToken()

B. firebase.messaging() is not initialized

C. getToken() returns a promise, not a direct value

D. console.log() cannot print tokens

Solution

1. Step 1: Verify permission requirement

   The code calls getToken() without first requesting notification permission using Notification.requestPermission().

2. Step 2: Consequence of missing permission

   Without granted permission, messaging.getToken() rejects the promise with an error, leading to an unhandled promise rejection error.

3. Final Answer:

   Missing permission request before calling getToken() -> Option A

4. Quick Check:

   Permission before getToken() [OK]

Hint: Request permission with Notification.requestPermission() before getToken() [OK]

Common Mistakes:

• Not using .then() or await with getToken()
• Forgetting to initialize Firebase
• Thinking console.log() cannot print tokens

5. You want to ensure your app always sends notifications to the correct device even if the FCM token changes. What is the best practice to handle token updates?

hard

A. Generate a new token manually every time the app starts

B. Store the token once and never update it

C. Listen for token refresh events and update your server with the new token

D. Ignore token changes because they rarely happen

Solution

1. Step 1: Understand token lifecycle

   FCM tokens can change, so apps must detect and handle updates.

2. Step 2: Use token refresh listener

   Listening for token refresh events lets the app send new tokens to the server to keep messaging accurate.

3. Final Answer:

   Listen for token refresh events and update your server with the new token -> Option C

4. Quick Check:

   Handle token refresh = update server [OK]

Hint: Always update server on token refresh events [OK]

Common Mistakes:

• Storing token once without updates
• Manually generating tokens incorrectly
• Ignoring token changes