Why optimistic UI improves perceived performance in Remix - See It in Action

Why optimistic UI improves perceived performance

📖 Scenario: You are building a simple comment submission feature for a blog post using Remix Framework. Users can add comments, and you want the app to feel fast and responsive.

🎯 Goal: Build a comment form that immediately shows the new comment on the screen before the server confirms it. This is called optimistic UI. It makes the app feel faster because users see their comment right away.

📋 What You'll Learn

Create a list of existing comments as initial data

Add a state variable to hold new comments optimistically

Implement a function to add a new comment to the state immediately when submitted

Complete the form to submit comments and update the UI optimistically

💡 Why This Matters

🌍 Real World

Optimistic UI is used in social media apps, chat apps, and any interactive web app to make the interface feel faster and smoother.

💼 Career

Understanding optimistic UI is important for frontend developers to improve user experience and build responsive applications.

1

Set up initial comments data

Create a constant called initialComments that is an array with these exact objects: { id: 1, text: 'Great post!' } and { id: 2, text: 'Thanks for sharing.' }.

Remix

# Your code here

Hint

Use const to create an array named initialComments with two comment objects.

2

Add state for optimistic comments

Add a React state variable called comments initialized with initialComments using useState.

Remix

const initialComments = [
  { id: 1, text: 'Great post!' },
  { id: 2, text: 'Thanks for sharing.' }
];

// Your code here

Hint

Use useState to create comments and setComments initialized with initialComments.

3

Add function to update comments optimistically

Write a function called addComment that takes a text parameter and updates comments by adding a new comment object with a unique id (use current timestamp) and the given text at the end of the array.

Remix

import { useState } from 'react';

const initialComments = [
  { id: 1, text: 'Great post!' },
  { id: 2, text: 'Thanks for sharing.' }
];

const [comments, setComments] = useState(initialComments);

// Your code here

Hint

Create addComment function that adds a new comment with id from Date.now() and the given text to comments.

4

Complete the comment form with optimistic UI

Add a form with an input and a submit button. On submit, prevent default, get the input value, call addComment with the input value, and clear the input. Render the comments array as a list of <li> elements showing each comment's text.

Remix

import { useState } from 'react';

const initialComments = [
  { id: 1, text: 'Great post!' },
  { id: 2, text: 'Thanks for sharing.' }
];

const [comments, setComments] = useState(initialComments);

function addComment(text) {
  const newComment = { id: Date.now(), text };
  setComments([...comments, newComment]);
}

// Your code here

Hint

Create a form with input and button. On submit, prevent default, call addComment with trimmed input, clear input, and render comments as list items.

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