mid · lesson 7 of 7

Perceived performance

Skeletons, optimism, work hiding.

Sidhanshu Monga·1 min·
You’ll be able to
  1. Choose between skeletons and spinners
  2. Apply optimistic updates safely
  3. Hide work with prefetching and early starts

Users do not experience milliseconds. They experience waiting. You can often make a product feel twice as fast without changing how long the work takes.

Show the shape early

Skeleton screens prepare the eye for the layout that is coming, so the arrival of content feels like a fill-in rather than a jump. Use them for content with a predictable structure, not for every spinner.

time
Skeleton vs spinner
A spinner says ‘something is happening, please wait.’ A skeleton says ‘this is the shape of what you’re about to see.’ One demands attention; the other prepares you.
#perceived performance#attention
Switch between the two and notice where your eye goes.

Be optimistic

For actions that almost always succeed, such as likes, toggles and reorders, apply the result immediately and reconcile with the server in the background. Roll back visibly if it fails.

time
Optimistic UI
Apply the change instantly; reconcile with the server in the background. The user never waits for the network for actions that almost always succeed.
#perceived performance#state
Same click, two strategies: update instantly, or wait for the server.

Hide work

  • Prefetch on hover or when a link enters the viewport
  • Start uploads as soon as a file is chosen, not on submit
  • Render the critical path first and defer the rest

The Optimistic UI and Skeleton vs spinner breakdowns go deeper into how each is built.

Try it

Record the slowest common interaction in your product. Apply one technique from this lesson and record it again. Compare how they feel, not the timings.

This lesson needs a hands-on exercise. The idea is sketched in issue #68. Build it and it ships here, with your name on it.
Key takeaways
01Users experience waiting, not milliseconds
02Be optimistic only where failure is rare and reversible
03Start work before the user asks for it