Notes

Micro-feedback and perceived speed

1 October 2026 2 min read

One button, three states and a spring. Change the network latency and the stiffness and feel why a button that answers at once feels faster than one that is.

  • Motion
  • Perceived performance
  • Interaction

A button has more than one look. It has a before, a while and an after, and the middle one is where people decide whether the interface is working or stuck.

9:41

Component

Place order

  1. 0.00 s idle
State trace
9:41

Autumn edit

Ridge overshirt

€189

Heavy cotton twill, boxy cut, corozo buttons.

  • Size and fit
  • Composition and care
  • Delivery and returns
M
Add to bag
Live component
9:41

Press feedback

Spring

0 s1 s
Stiffness
180
Damping ratio
0.5
Overshoot
16%
Button scale
1.000
Spring response

Parameters
Change them, then press the button again.

800 ms
180
Live demo. Everything runs in your browser. Now try to break it.
MicroFeedback.svelte, 271 lines

Press "Place order" in the middle handset. The left one logs every state change with its time. The right one draws the spring that moves the button when you press it.

What happens while you wait

The bar inside the button fills in exactly as long as the network latency you set. It is not a measurement of progress, it is a promise about how long this will take. Slide the latency to 0 and the loading state barely shows. Slide it to two seconds and the bar is the only thing that tells you the tap counted.

Three states are enough: idle, loading, done. The label changes with each one ("Place order", "Placing order", "Order placed"), so the state is also readable without colour and by a screen reader, which hears the change.

The press

The button shrinks a little when you press it and springs back. That reaction starts at the first frame, long before any server has answered. It is the cheapest feedback there is: it only says "I felt that".

The spring has a fixed damping ratio. You change its stiffness, and the third handset shows what that does: stiff springs snap back with little overshoot, soft ones wobble. Too much wobble on a button reads as toy-like, too little as dead.

What to take from it

  • Answer the finger first. A pressed state within one frame, then do the work.
  • Give the wait a shape. A bar, a changed label, anything that shows the tap was understood.
  • Name the end. A done state that stays for a moment tells people they can stop watching.
  • Respect reduced motion. With the setting on, the button changes scale instantly instead of springing. Turn on "No motion" under the demo to see it.

Related: Springs keep their momentum is about why this spring is not a Bézier curve, and Fast is a feeling is about what changes when the interface answers before the server does.

Related

How bright was it?

Five lamps and an optional line. Feedback, a bug, an idea, anything. I read every one and sum them up once a month.

Pick a lamp

Stored without name, address or cookie, and deleted after a year. Details in the privacy notice.