Skip to main content
UI Guides

Search rules

Search all UI Guides rules by name, category, or source

interactionsVercel

Optimistic Updates

SHOULD

SHOULD: Optimistic UI; reconcile on response; on failure show error and rollback or offer Undo

Update UI immediately when success is likely; reconcile on response

Bad

Good

Why it matters

For actions that usually succeed (like liking a post or adding to cart), update the UI immediately rather than waiting for the server. This makes the interface feel instant. If the request fails, show an error and revert the change or offer an undo option.

References

Built by Gleb Stroganov, design engineer at Evil Martians.

The rules come from other people's skills and guidelines — Vercel, Rauno Freiberg, @Ibelick, impeccable, Emil Kowalski, Tailwind, RAMS — each one credited on the Sources page. The work here is extraction and wiring: every rule is pulled into one corpus, given a good and a bad example you can operate, a MUST/SHOULD/NEVER rule an agent can paste, and a link back to where it came from.