Why optimistic UI improves perceived performance in Remix

Introduction

Optimistic UI makes apps feel faster by showing changes right away, even before the server confirms them.

When a user submits a form and you want to show the result immediately.

When updating a list item and you want the change to appear without waiting.

When liking or favoriting something and you want instant feedback.

When deleting an item and you want it to disappear right away.

When toggling a setting and you want the UI to reflect the change instantly.

Syntax

Remix

function handleAction() {
  const oldValue = state;
  // Update UI immediately
  setState(newValue);

  // Send request to server
  fetch('/api/update', { method: 'POST', body: JSON.stringify(newValue) })
    .then(response => response.json())
    .catch(() => {
      // Revert UI if server fails
      setState(oldValue);
    });
}

Update the UI state before waiting for the server response.

Handle errors by reverting the UI if the server rejects the change.

Examples

Show the new likes count right away, then update the server.

Remix

setLikes(likes + 1); // Immediately update likes count
await sendLikeToServer(); // Then send to server

Remove the item from the list immediately, then confirm deletion on server.

Remix

setItems(items.filter(item => item.id !== id)); // Remove item from UI
await deleteItemFromServer(id); // Then delete on server

Sample Program

This component shows a like button that updates the count immediately when clicked. If the server call fails, it reverts the count and shows an error message.

Remix

import { useState } from 'react';

export default function LikeButton() {
  const [likes, setLikes] = useState(0);
  const [error, setError] = useState(null);

  async function handleLike() {
    const oldLikes = likes;
    setLikes(likes + 1); // Optimistic update

    try {
      const response = await fetch('/api/like', { method: 'POST' });
      if (!response.ok) throw new Error('Failed to like');
    } catch {
      setLikes(oldLikes); // Revert on error
      setError('Could not update like');
    }
  }

  return (
    <div>
      <button onClick={handleLike} aria-label="Like button">
        Like ({likes})
      </button>
      {error && <p role="alert" style={{ color: 'red' }}>{error}</p>}
    </div>
  );
}

Important Notes

Optimistic UI improves user experience by reducing waiting time.

Always handle errors to keep UI consistent with server state.

Use clear feedback like error messages if something goes wrong.

Summary

Optimistic UI shows changes immediately to make apps feel faster.

It updates the UI before the server confirms the action.

Errors must be handled to keep UI and data in sync.

Practice

1. What is the main reason optimistic UI improves perceived performance in Remix apps?

easy

A. It shows UI changes immediately before server confirmation

B. It waits for the server response before updating UI

C. It disables user input during server requests

D. It reloads the entire page after each action

Solution

1. Step 1: Understand optimistic UI behavior

   Optimistic UI updates the interface immediately when a user acts, without waiting for the server.

2. Step 2: Compare with other options

   Waiting for server or reloading page delays UI feedback, reducing perceived speed.

3. Final Answer:

   It shows UI changes immediately before server confirmation -> Option A

4. Quick Check:

   Immediate UI update = D [OK]

Hint: Optimistic UI updates instantly, no waiting for server [OK]

Common Mistakes:

• Thinking UI waits for server response
• Confusing optimistic UI with disabling input
• Assuming page reload improves speed

2. Which code snippet correctly shows an optimistic UI update in Remix using useFetcher?

easy

A. fetcher.submit(data); updateUIImmediately();

B. await fetcher.submit(data); updateUIImmediately();

C. fetcher.load('/data'); updateUIAfterLoad();

D. fetcher.reset(); updateUIAfterReset();

Solution

1. Step 1: Identify optimistic UI pattern

   Optimistic UI updates UI immediately, so updateUIImmediately() must run without waiting.

2. Step 2: Analyze code snippets

   fetcher.submit(data); updateUIImmediately(); calls submit then updates UI immediately. await fetcher.submit(data); updateUIImmediately(); waits (await) before UI update, not optimistic.

3. Final Answer:

   fetcher.submit(data); updateUIImmediately(); -> Option A

4. Quick Check:

   Immediate UI update after submit = B [OK]

Hint: Optimistic UI updates before awaiting server response [OK]

Common Mistakes:

• Using await before UI update
• Confusing fetcher.load with submit
• Resetting fetcher instead of submitting

3. Given this Remix code snippet, what will the user see immediately after clicking the submit button?

const fetcher = useFetcher();
function handleClick() {
  fetcher.submit({ text: 'Hello' });
  setMessage('Sending...');
}

medium

A. An error message appears immediately

B. The message updates only after server response

C. No message appears until page reload

D. The message 'Sending...' appears immediately

Solution

1. Step 1: Understand the code flow

   handleClick calls fetcher.submit then immediately sets message to 'Sending...'.

2. Step 2: Determine UI update timing

   setMessage runs immediately, so UI shows 'Sending...' right after click.

3. Final Answer:

   The message 'Sending...' appears immediately -> Option D

4. Quick Check:

   Immediate setState update = A [OK]

Hint: UI updates right after setState call, no wait needed [OK]

Common Mistakes:

• Assuming message waits for server
• Thinking submit blocks UI update
• Confusing fetcher.submit with fetcher.load

4. Identify the bug in this optimistic UI code snippet:

const fetcher = useFetcher();
function handleSubmit(data) {
  fetcher.submit(data);
  setItems([...items, data]);
}
// Later, if server rejects, no rollback is done

medium

A. setItems mutates state directly instead of copying

B. fetcher.submit is called incorrectly without await

C. No error handling to revert UI on server failure

D. handleSubmit is missing event.preventDefault()

Solution

1. Step 1: Review optimistic UI update

   UI updates immediately by adding data to items before server confirms.

2. Step 2: Check error handling

   No rollback or error handling means UI can show wrong data if server rejects.

3. Final Answer:

   No error handling to revert UI on server failure -> Option C

4. Quick Check:

   Missing rollback on failure = C [OK]

Hint: Optimistic UI needs rollback on server error [OK]

Common Mistakes:

• Thinking await is required for optimistic update
• Confusing state mutation with copying
• Assuming preventDefault is always needed

5. In a Remix app, you want to implement optimistic UI for adding comments. Which approach best ensures perceived performance and data consistency?

hard

A. Wait for server response before updating UI to avoid inconsistencies

B. Update UI immediately, then rollback if server rejects, showing error message

C. Reload the page after server confirms to show new comment

D. Disable comment input until server responds to prevent errors

Solution

1. Step 1: Understand optimistic UI goals

   Optimistic UI updates UI immediately to feel fast but must handle errors to stay consistent.

2. Step 2: Evaluate options for consistency

   Update UI immediately, then rollback if server rejects, showing error message updates UI immediately and rolls back on error, balancing speed and correctness.

3. Final Answer:

   Update UI immediately, then rollback if server rejects, showing error message -> Option B

4. Quick Check:

   Optimistic update + rollback = A [OK]

Hint: Optimistic UI needs rollback on failure for consistency [OK]

Common Mistakes:

• Waiting for server loses perceived speed
• Reloading page is slow and jarring
• Disabling input reduces user experience