Preview channels in Firebase - Time & Space Complexity

Time Complexity: Preview channels

O(n)

Understanding Time Complexity

When using preview channels in Firebase Hosting, it's important to understand how the time to deploy and update grows as you use more channels.

We want to know how the number of preview channels affects the work Firebase does behind the scenes.

Scenario Under Consideration

Analyze the time complexity of deploying to multiple preview channels.

// Deploy to a preview channel
firebase hosting:channel:deploy channel-name

// List all preview channels
firebase hosting:channel:list

// Delete a preview channel
firebase hosting:channel:delete channel-name

This sequence shows creating, listing, and deleting preview channels in Firebase Hosting.

Identify Repeating Operations

• Primary operation: API calls to create, list, or delete each preview channel.
• How many times: Once per channel for creation and deletion; listing fetches all channels at once.

How Execution Grows With Input

As the number of preview channels grows, the time to list all channels grows too, because Firebase must fetch info for each channel.

Input Size (n)	Approx. API Calls/Operations
10	About 10 calls to create/delete, 1 call to list all 10
100	About 100 calls to create/delete, 1 call to list all 100
1000	About 1000 calls to create/delete, 1 call to list all 1000

Pattern observation: Creating or deleting scales linearly with number of channels; listing is a single call but returns data proportional to number of channels.

Final Time Complexity

Time Complexity: O(n)

This means the time to manage preview channels grows directly with how many channels you have.

Common Mistake

[X] Wrong: "Listing preview channels takes the same time no matter how many channels exist."

[OK] Correct: Listing returns info for every channel, so more channels mean more data to fetch and process, increasing time.

Interview Connect

Understanding how operations scale with input size shows you can think about cloud services beyond just writing code. This skill helps you design better systems and explain your choices clearly.

Self-Check

"What if Firebase allowed batch creation of preview channels? How would that change the time complexity?"

Practice

1. What is the main purpose of Firebase preview channels?

easy

A. To create temporary, shareable versions of your app for testing

B. To permanently host your live app

C. To backup your Firebase database

D. To monitor app usage statistics

Solution

1. Step 1: Understand preview channels concept

   Preview channels allow you to create temporary versions of your app that you can share for testing.

2. Step 2: Compare with other options

   Permanent hosting, backups, and monitoring are different Firebase features unrelated to preview channels.

3. Final Answer:

   To create temporary, shareable versions of your app for testing -> Option A

4. Quick Check:

   Preview channels = temporary test versions [OK]

Hint: Preview channels = temporary test app versions [OK]

Common Mistakes:

• Confusing preview channels with permanent hosting
• Thinking preview channels backup data
• Assuming preview channels track usage

2. Which command correctly creates a Firebase preview channel named test123?

easy

A. firebase hosting:channel:deploy test123

B. firebase deploy --channel test123

C. firebase hosting:deploy test123

D. firebase channel:create test123

Solution

1. Step 1: Recall the correct Firebase CLI command

   The command to create a preview channel is firebase hosting:channel:deploy CHANNEL_ID.

2. Step 2: Match the command with the channel name

   Replacing CHANNEL_ID with test123 gives firebase hosting:channel:deploy test123.

3. Final Answer:

   firebase hosting:channel:deploy test123 -> Option A

4. Quick Check:

   Correct CLI command = firebase hosting:channel:deploy test123 [OK]

Hint: Use hosting:channel:deploy with your channel name [OK]

Common Mistakes:

• Using deploy without hosting:channel
• Using channel:create which is invalid
• Mixing command order or flags

3. What happens when you deploy to a Firebase preview channel with the command firebase hosting:channel:deploy preview1?

medium

A. The live app is overwritten immediately

B. The app is published to the app stores

C. The Firebase database is reset

D. A temporary URL is created to share the app version

Solution

1. Step 1: Understand the effect of deploying to a preview channel

   Deploying to a preview channel creates a temporary, shareable URL for testing.

2. Step 2: Eliminate incorrect options

   It does not overwrite the live app, reset databases, or publish to app stores.

3. Final Answer:

   A temporary URL is created to share the app version -> Option D

4. Quick Check:

   Deploy to preview channel = temporary URL [OK]

Hint: Deploying preview channel creates temporary share URL [OK]

Common Mistakes:

• Thinking it overwrites live app immediately
• Confusing preview deploy with database reset
• Assuming it publishes app to stores

4. You ran firebase hosting:channel:deploy MyTest but got an error saying the channel name is invalid. What is a likely cause?

medium

A. You need to be logged out of Firebase CLI

B. You must include the --force flag

C. Channel names cannot contain uppercase letters

D. Channel names must be numeric only

Solution

1. Step 1: Check Firebase preview channel naming rules

   Channel names must be lowercase alphanumeric and can include dashes, but no uppercase letters.

2. Step 2: Evaluate other options

   --force flag is not required for naming; numeric-only names are not required; being logged out causes authentication errors, not naming errors.

3. Final Answer:

   Channel names cannot contain uppercase letters -> Option C

4. Quick Check:

   Invalid channel name = uppercase letters [OK]

Hint: Use only lowercase letters in channel names [OK]

Common Mistakes:

• Trying uppercase letters in channel names
• Assuming --force fixes naming errors
• Confusing auth errors with naming errors

5. You want to share a new feature with your team without affecting the live app. Which steps correctly use Firebase preview channels to do this?

hard

A. Run firebase deploy to update live app, then email the team

B. Run firebase hosting:channel:deploy featureX and share the generated URL

C. Create a new Firebase project and deploy the app there

D. Use firebase hosting:disable to stop live hosting temporarily

Solution

1. Step 1: Identify the correct way to create a preview version

   Using firebase hosting:channel:deploy featureX creates a temporary preview channel for sharing.

2. Step 2: Understand why other options are incorrect

   Deploy updates live app; creating new project is unnecessary; disabling hosting stops live app, not preview.

3. Final Answer:

   Run firebase hosting:channel:deploy featureX and share the generated URL -> Option B

4. Quick Check:

   Preview channel deploy + share URL = safe testing [OK]

Hint: Deploy preview channel and share URL, not live deploy [OK]

Common Mistakes:

• Deploying directly to live app by mistake
• Creating new projects unnecessarily
• Disabling hosting instead of previewing