Firebase with Flutter - Time & Space Complexity

Time Complexity: Firebase with Flutter

O(n)

Understanding Time Complexity

When using Firebase with Flutter, it is important to understand how the number of operations grows as your app handles more data.

We want to know how the time to fetch or write data changes when the amount of data increases.

Scenario Under Consideration

Analyze the time complexity of reading multiple documents from Firestore in Flutter.

final firestore = FirebaseFirestore.instance;

Future fetchUsers(List userIds) async {
  for (var id in userIds) {
    var doc = await firestore.collection('users').doc(id).get();
    print(doc.data());
  }
}
    

This code fetches user data one by one for each user ID in the list.

Identify Repeating Operations

Look at what repeats as the input list grows.

• Primary operation: Firestore document read API call (doc(id).get())
• How many times: Once for each user ID in the input list

How Execution Grows With Input

Each user ID causes one separate read call, so the total calls grow directly with the number of users.

Input Size (n)	Approx. Api Calls/Operations
10	10 document reads
100	100 document reads
1000	1000 document reads

Pattern observation: The number of API calls grows linearly as the input size increases.

Final Time Complexity

Time Complexity: O(n)

This means the time to fetch data grows directly in proportion to the number of user IDs.

Common Mistake

[X] Wrong: "Fetching multiple documents one by one is as fast as fetching them all at once."

[OK] Correct: Each separate fetch makes a network call, so doing them one by one takes longer as the list grows.

Interview Connect

Understanding how your app's data fetching scales helps you build smoother apps and shows you know how to handle real-world data growth.

Self-Check

"What if we used a single query to fetch all user documents at once? How would the time complexity change?"