Limit and pagination in Firebase - Step-by-Step Execution

Process Flow - Limit and pagination

Start Query

↓

Apply Limit N

↓

Fetch First N Items

↓

Display Items

↓

User Requests Next Page

↓

Use Last Item as Cursor

↓

Fetch Next N Items After Cursor

↓

Repeat Display and Pagination

The query first limits results to N items, then uses the last item as a cursor to fetch the next page when requested.

Execution Sample

Firebase

db.collection('posts')
  .orderBy('date')
  .limit(3)
  .get()
  .then(snapshot => {
    // display first 3 posts
  })

Fetches the first 3 posts ordered by date from the database.

Process Table

Step	Action	Query State	Result	Notes
1	Start query with orderBy('date')	No limit, no cursor	Query ready	Initial query setup
2	Apply limit(3)	Limit set to 3	Query ready	Limits results to 3 items
3	Execute get()	Limit=3, no cursor	Fetch first 3 posts	Returns first page
4	Display posts	Showing 3 posts	Posts 1,2,3 shown	User sees first page
5	User requests next page	Cursor set to last post (post 3)	Prepare next query	Use last item as cursor
6	Query with startAfter(post 3) and limit(3)	Limit=3, cursor=post 3	Fetch posts after post 3	Fetch next page
7	Execute get()	Limit=3, cursor=post 3	Fetch posts 4,5,6	Returns second page
8	Display posts	Showing posts 4,5,6	Posts 4,5,6 shown	User sees second page
9	User requests next page	Cursor set to last post (post 6)	Prepare next query	Repeat pagination
10	Query with startAfter(post 6) and limit(3)	Limit=3, cursor=post 6	Fetch posts after post 6	Fetch third page
11	Execute get()	Limit=3, cursor=post 6	Fetch posts 7,8,9	Returns third page
12	Display posts	Showing posts 7,8,9	Posts 7,8,9 shown	User sees third page
13	User requests next page	Cursor set to last post (post 9)	Prepare next query	If no more posts, empty result
14	Query with startAfter(post 9) and limit(3)	Limit=3, cursor=post 9	Fetch posts after post 9	No more posts
15	Execute get()	Limit=3, cursor=post 9	Empty result	No more pages
16	Display posts	No posts to show	Empty page	Pagination ends

💡 No more posts after last cursor, pagination ends

Status Tracker

Variable	Start	After Step 3	After Step 7	After Step 11	After Step 15
limit	undefined	3	3	3	3
cursor	undefined	post 3	post 6	post 9	post 9
fetchedPosts	[]	[post1, post2, post3]	[post4, post5, post6]	[post7, post8, post9]	[]

Key Moments - 3 Insights

Why do we need to use the last item as a cursor for the next page?

Because Firebase queries use cursors to know where to start fetching next items. The last item of the current page marks the starting point for the next query (see steps 5 and 6 in execution_table).

What happens if we don't use limit() in the query?

Without limit(), the query fetches all matching items at once, which can be slow and inefficient. Limit controls how many items are fetched per page (see step 2).

Why does the pagination stop after some pages?

Pagination stops when the query returns no more items after the cursor, meaning all data has been fetched (see steps 14-16).

Visual Quiz - 3 Questions

Look at the execution_table at step 7, how many posts are fetched?

A 3 posts

B 6 posts

C No posts

D 1 post

💡 Hint

Check the 'Result' column at step 7 in execution_table

At which step does the cursor first get set to post 6?

A Step 7

B Step 5

C Step 9

D Step 3

💡 Hint

Look at the 'cursor' variable changes in variable_tracker after each step

If we change limit(3) to limit(5), how would the fetchedPosts array change after step 3?

A It would fetch 3 posts still

B It would fetch 5 posts instead of 3

C It would fetch no posts

D It would fetch all posts

💡 Hint

Limit controls how many posts are fetched per query (see step 2 and variable_tracker)

Concept Snapshot

Firebase pagination uses limit() to fetch a fixed number of items.
Use startAfter(lastItem) as a cursor to fetch the next page.
Repeat queries with updated cursor to paginate through data.
Stop when query returns no more items.
This approach avoids loading all data at once and improves performance.

Full Transcript

This visual execution shows how Firebase limit and pagination work step-by-step. First, a query orders posts by date and limits results to 3 items. The first 3 posts are fetched and displayed. When the user requests the next page, the last post from the previous page is used as a cursor with startAfter() to fetch the next 3 posts. This process repeats until no more posts are available, ending pagination. Variables like limit, cursor, and fetchedPosts change as the query progresses. Key moments clarify why cursors and limits are needed and when pagination stops. The quiz tests understanding of fetched items, cursor updates, and limit effects. This method efficiently loads data in pages rather than all at once.