Optimistic state updates in NextJS - Step-by-Step Execution

Concept Flow - Optimistic state updates

User triggers update

↓

Update UI state immediately

↓

Send update request to server

↓

Server responds

↓

Keep UI

The UI updates right away when the user acts, then waits for the server. If the server says no, the UI goes back.

Execution Sample

NextJS

const [count, setCount] = useState(0);

async function increment() {
  setCount(prevCount => prevCount + 1); // optimistic update
  const res = await fetch('/api/increment', { method: 'POST' });
  if (!res.ok) setCount(prevCount => prevCount - 1); // rollback on failure
}

This code increases a counter on the screen immediately, then tries to update the server. If the server fails, it resets the counter.

Execution Table

Step	Action	UI State (count)	Server Response	Resulting UI State
1	User clicks increment	0	N/A	0
2	Optimistic update: setCount(count + 1)	1	Waiting	1
3	Send POST to /api/increment	1	Waiting	1
4	Server responds OK	1	Success	1
5	No rollback needed	1	Success	1
6	User clicks increment again	1	N/A	1
7	Optimistic update: setCount(count + 1)	2	Waiting	2
8	Send POST to /api/increment	2	Waiting	2
9	Server responds ERROR	2	Failure	2
10	Rollback: setCount(previous count)	1	Failure	1

💡 Execution stops after rollback or confirmation from server.

Variable Tracker

Variable	Start	After Step 2	After Step 4	After Step 7	After Step 9	Final
count	0	1	1	2	2	1

Key Moments - 3 Insights

Why does the UI update before the server confirms?

The UI updates immediately to keep the app feeling fast and responsive, as shown in step 2 and 7 of the execution_table.

What happens if the server rejects the update?

The UI rolls back to the previous state to stay correct, as seen in step 10 where count goes back from 2 to 1.

Why do we keep track of the old state?

We save the old state so we can restore it if the server rejects the change, demonstrated by resetting count in step 10.

Visual Quiz - 3 Questions

Look at the execution_table, what is the UI state (count) immediately after the optimistic update in step 2?

A 1

B 0

C 2

D Undefined

💡 Hint

Check the 'UI State (count)' column at step 2 in the execution_table.

At which step does the UI rollback happen due to server failure?

A Step 4

B Step 10

C Step 9

D Step 7

💡 Hint

Look for the step where 'Rollback' is mentioned in the 'Action' column.

If the server always responds successfully, how would the final UI state after two increments change?

A It would rollback to 0

B It would stay at 1

C It would be 2

D It would be undefined

💡 Hint

Refer to the 'Resulting UI State' column after successful server responses in the execution_table.

Concept Snapshot

Optimistic state updates:
- Update UI immediately on user action
- Send server request in background
- If server confirms, keep UI
- If server rejects, rollback UI
- Makes app feel fast and responsive

Full Transcript

Optimistic state updates mean the app changes what you see right away when you do something, like clicking a button. Then it asks the server to save that change. If the server says yes, the app keeps the change. If the server says no, the app goes back to how it was before. This way, the app feels quick and smooth. In the example, when you click increment, the number on screen goes up immediately. Then the app sends a request to the server. If the server fails, the number goes back down. This helps users feel the app is fast even if the server is slow.

Practice

1. What is the main purpose of optimistic state updates in Next.js applications?

easy

A. To delay UI updates until the server responds

B. To prevent any UI changes until the user refreshes the page

C. To update the UI immediately before the server confirms the change

D. To disable user interactions during server requests

Solution

1. Step 1: Understand optimistic updates concept

   Optimistic updates update the UI immediately to make the app feel faster.

2. Step 2: Compare options with concept

   Only To update the UI immediately before the server confirms the change describes updating UI before server confirmation, matching optimistic updates.

3. Final Answer:

   To update the UI immediately before the server confirms the change -> Option C

4. Quick Check:

   Optimistic update = immediate UI change [OK]

Hint: Optimistic means acting before confirmation [OK]

Common Mistakes:

• Thinking UI waits for server response
• Confusing optimistic with pessimistic updates
• Assuming UI disables interactions

2. Which of the following is the correct way to implement an optimistic update using React's useState in Next.js?

easy

A. Use setTimeout to delay state update by 2 seconds

B. Update state after server response inside then()

C. Do not update state at all until server confirms

D. Update state immediately before sending server request

Solution

1. Step 1: Recall optimistic update timing

   Optimistic updates change state immediately before server response.

2. Step 2: Match options to timing

   Update state immediately before sending server request updates state immediately before request, fitting optimistic update pattern.

3. Final Answer:

   Update state immediately before sending server request -> Option D

4. Quick Check:

   Immediate state update = optimistic update [OK]

Hint: Update state before server reply for optimism [OK]

Common Mistakes:

• Waiting for server response before updating state
• Delaying state update unnecessarily
• Not updating state at all

3. Consider this Next.js React component snippet using optimistic updates:

const [count, setCount] = useState(0);

async function increment() {
  setCount(count + 1); // optimistic update
  try {
    await fetch('/api/increment', { method: 'POST' });
  } catch {
    setCount(count); // revert on failure
  }
}

What will be the displayed count if the server request fails?

medium

A. The count reverts to the original value before increment

B. The count becomes undefined

C. The count resets to 0 regardless

D. The count remains incremented by 1

Solution

1. Step 1: Analyze optimistic update and revert logic

   Count increments immediately, but on fetch failure, count resets to original value.

2. Step 2: Understand revert on failure

   The catch block sets count back to original, undoing optimistic increment.

3. Final Answer:

   The count reverts to the original value before increment -> Option A

4. Quick Check:

   Failed fetch triggers revert = original count [OK]

Hint: Revert state on error to original value [OK]

Common Mistakes:

• Assuming optimistic update stays after failure
• Thinking count resets to zero always
• Ignoring catch block revert

4. Given this code snippet for optimistic updates in Next.js:

const [items, setItems] = useState([]);

async function addItem(newItem) {
  setItems([...items, newItem]);
  try {
    await fetch('/api/add', { method: 'POST', body: JSON.stringify(newItem) });
  } catch {
    // What is missing here?
  }
}

What is the best fix to handle errors properly?

medium

A. Remove the optimistic update and update only after fetch

B. Add code to revert items state to previous value in catch

C. Ignore errors since optimistic update is enough

D. Add a console.log in catch without state change

Solution

1. Step 1: Identify missing error handling

   Optimistic update changes state immediately, but no revert on failure.

2. Step 2: Add revert logic in catch block

   To keep UI consistent, revert items to previous state if fetch fails.

3. Final Answer:

   Add code to revert items state to previous value in catch -> Option B

4. Quick Check:

   Revert state on error = correct error handling [OK]

Hint: Revert state in catch to fix errors [OK]

Common Mistakes:

• Not reverting state on failure
• Removing optimistic update unnecessarily
• Only logging errors without UI fix

5. You want to implement optimistic updates for a list of tasks in Next.js. The user can add a task, and the UI should update immediately. However, if the server rejects the addition, the UI must revert. Which approach correctly handles this scenario?

hard

A. Update the tasks state immediately, then on server failure, reset tasks to previous state saved before update

B. Wait for server confirmation before updating tasks state to avoid inconsistencies

C. Update tasks state immediately and do nothing on failure, assuming server will eventually succeed

D. Clear the tasks list on server failure to force user refresh

Solution

1. Step 1: Understand optimistic update with revert

   Optimistic update means immediate UI change, but must revert on failure to keep UI correct.

2. Step 2: Evaluate options for correct revert handling

   Update the tasks state immediately, then on server failure, reset tasks to previous state saved before update saves previous state and reverts on failure, matching best practice.

3. Final Answer:

   Update the tasks state immediately, then on server failure, reset tasks to previous state saved before update -> Option A

4. Quick Check:

   Optimistic update + revert = Update the tasks state immediately, then on server failure, reset tasks to previous state saved before update [OK]

Hint: Save old state to revert if server fails [OK]

Common Mistakes:

• Not reverting UI on failure
• Waiting for server before UI update
• Clearing list unnecessarily on error