Spinners

Spinners are what an interface shows while it waits: a shape moving at a constant rate to say work is in flight without pretending to know when it ends. This family carries both halves of waiting. Three indeterminate sweeps, built from eight arms, eight dots, and a pair of opposed arcs over a soft ring, sit beside a progress ring small enough to live in a list row, a queue of bars with a total and an estimate, a rolling percentage for a blocking wait, and a panel that names each step as it runs.

Choosing between them is a question about duration, not style. A wait too short to notice is better served by nothing at all, since a spinner that appears and vanishes reads as a glitch. A wait long enough for someone to wonder whether it has hung needs more than a sweep, because a spin that never changes looks identical to a freeze. That is where elapsed time, a percentage, or a named step list earns its place.

15 blocks

Spinner

Work with no measurable end: a request in flight, a permission check

Spinner, morph

A spinner that should end in an answer, in a row, a section or a button

Spinner, ticks

A long wait that should visibly move on

Progress circle

Limits and quotas: a ring small enough to sit in a row and still carry its own number

Progress circle, morph

One limit at a time, with its detail

Progress circle, ticks

Usage you can count

Progress bar

A long job with a real end: an import, a migration, a download

Progress bar, morph

A job whose whole progress is the one number

Progress bar, ticks

A job where small changes should be countable

Percentage indicator

The one number a full-screen or blocking wait is about

Percentage indicator, morph

A blocking wait where the card itself is the bar

Percentage indicator, ticks

A blocking wait that wants a scale to read against

Processing panel

A job with named steps, where the wait needs to say what it is doing, not just that it is

Processing panel, morph

A job where only the running step needs attention

Processing panel, ticks

A job where the timeline and the history both matter

01

Using Spinners

Reach for it when

  • A request whose duration you cannot estimate: an auth check, a permission lookup
  • A button that has been submitted and must not be pressed a second time
  • A quota ring small enough to sit inside a list row and still carry its number
  • A blocking wait where one number is the entire message

Reach for something else when

  • Content arriving into a known layout: a skeleton holds the shape and stops the jump
  • A job with named stages: a step list says which stage is slow; a sweep says nothing
  • A wait short enough to flash: show nothing and let the result land
02

Where it shows up

01

Submit button state

A form button that has been pressed and is waiting on the server. The spinner replaces the label or sits beside it, the button goes disabled, and a second press cannot create a second record.

02

Plan limit rings

A billing page listing each limit with a small ring beside it. The rings are scanned at a glance for the ones near the top, and the used-of-total figure next to each one carries the detail.

03

Import queues

Files processed one after another, each with its own bar and status and a footer totalling the work left. The queue answers which item is slow, which a single aggregate bar cannot.

04

Full-screen migrations

A blocking wait during an account or data move, where the percentage is the whole message. The heading says what is running, the rolling number carries the progress, and one control offers the way out.

03

Questions

What is the difference between a determinate and an indeterminate spinner?

An indeterminate spinner moves at a constant rate and carries no value; it says only that work is happening. A determinate one, a ring or a bar that fills, reports a fraction of a known total. The rule of thumb is that if the fraction cannot be computed honestly, do not draw one, because a determinate ring that stalls is read as a broken product.

Should a loading spinner respect reduced motion preferences?

All blocks
The Orvain Dispatch

Premium components, free in your inbox.

Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.

Just components, never spam. You can unsubscribe anytime.