การตอบสนองทันทีด้วย useOptimistic

When a user clicks a like button, the change has to travel to the server and back before the UI reflects it. On a slow network that delay feels broken.

The fix is optimistic UI: assume the action will succeed, update the screen instantly, and reconcile with the server once it responds. If the server fails, you roll back automatically.

React 19 (shipped with Next.js 15) gives you a dedicated hook for this: useOptimistic.

useOptimistic takes your real state and an update function, and returns a temporary optimistic value plus a function to apply optimistic changes.

• optimisticState — what you render right now
• addOptimistic(value) — queue an optimistic change

The signature is useOptimistic(state, (currentState, optimisticValue) => newState). The reducer-style function merges the optimistic value into the current state.

First, the real work happens in a Server Action. It runs on the server, mutates the database, and revalidates the cache.

Notice the "use server" directive and the revalidatePath call so other parts of the app see the fresh count.

In a Client Component, we hold the optimistic like state. When clicked, we call addOptimistic first (instant UI), then await the Server Action.

If the action throws, React automatically discards the optimistic value and reverts to the real likes prop.

Optimistic updates must happen inside a transition. Calling addOptimistic outside one throws an error.

• Use useTransition for button clicks, or
• Use <form action={...}> — form actions are wrapped in a transition automatically

The transition tells React the update is non-urgent and tied to a pending async action. When the action finishes (and revalidation arrives), the optimistic value is replaced by the real one.

For adding a comment, the form's action already runs in a transition, so you can call addOptimistic directly inside it.

We append a temporary comment (with a sending flag) so the user sees it immediately, then submit to the server.

useOptimistic does not change your real state. It layers a temporary view on top.

• The base state is your prop/state from the server.
• The optimistic value lives only while a transition is pending.
• When the transition settles, React throws the optimistic value away and re-renders from the (now updated) base state.

This is why rollback is free: there is nothing to undo, you simply stop showing the optimistic layer.

The update function is just a pure reducer. You can model any toggle — likes, bookmarks, follow/unfollow — by switching a boolean and deriving counts.

Because it is pure, you can unit-test it without React. Here is a standalone reducer that mirrors what we pass to useOptimistic.

If the Server Action rejects, React reverts the optimistic state, but the user should know why. Wrap the action in try/catch and surface an error (a toast, an inline message).

The optimistic value disappears automatically; your job is only to communicate the failure.

For automatic reconciliation to work, the base state must come from the server and refresh after the mutation. Two common ways:

• revalidatePath / revalidateTag inside the Server Action re-fetches the page data.
• Passing fresh props down to the Client Component (e.g. from a Server Component parent).

If the base state never updates, the optimistic value will vanish and snap back to the old count — a classic flicker bug.

You could fake optimism with useState, but you would have to manually save the previous value, write rollback logic, and clear it after the request. That is error-prone.

• useOptimistic ties the optimistic value to the transition lifecycle — auto-applied while pending, auto-discarded when settled.
• It re-syncs whenever the base state changes, so server truth always wins.

Reach for useOptimistic whenever an action has a clear, predictable success outcome you can show immediately.

You learned how to deliver instant feedback with useOptimistic in Next.js 15:

• useOptimistic(state, reducer) returns an optimistic view plus an addOptimistic function.
• Optimistic updates must run inside a transition (via useTransition or a form action).
• The real mutation lives in a Server Action that calls revalidatePath/revalidateTag so the base state refreshes.
• On success the optimistic layer is replaced by server truth; on failure React auto-reverts — you just surface an error.
• Prefer it over manual useState rollback for likes, comments, and toggles.