# Progress Indicator

A progress indicator communicates that work is underway and, when measurable, how much of the operation is complete.

- Type: artifact
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-09-24
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/progress-indicator/>)

## What it means

A determinate progress indicator represents measurable completion, often as a bar or percentage. An indeterminate indicator shows ongoing activity when remaining work cannot be estimated. A spinner is one visual form of indeterminate feedback, not evidence that the system is making meaningful progress.

## Why it matters

Visible, accurate progress reduces uncertainty during delays and helps users decide whether to wait, cancel, or do something else. Misleading progress damages trust, while unexplained animation can make a stalled operation appear healthy.

## When to use it

Use determinate progress for operations with a defensible total, such as uploading known bytes or completing defined steps. Use indeterminate feedback for brief work with an unknown duration, then switch when a reliable estimate becomes available. For long background tasks, consider notification instead of requiring users to watch.

## How it works

1. Identify the operation, expected duration, measurable total, and whether users can safely pause or cancel.
2. Choose determinate feedback only when advancement can be represented honestly.
3. Label the operation and expose current value, minimum, maximum, and status programmatically when relevant.
4. Keep updates stable and meaningful, and explain stalls, failures, or unusually long phases.
5. Confirm completion and transition to the resulting state rather than leaving an indicator at 100 percent.

## A practical example

A data-export tool initially shows “Preparing export” with indeterminate status. Once records are counted, it switches to a determinate bar with processed and total values, permits safe cancellation, and replaces the bar with a download link on completion.

## Where it breaks

Estimates are unreliable when work varies or depends on a network, and artificial smoothing can mislead. Frequent announcements overwhelm screen-reader users, while motion can distract or conflict with reduced-motion preferences.

## Common mistakes

- Showing a percentage that is not tied to real progress.
- Using an endless spinner without timeout, explanation, or recovery.
- Announcing every tiny progress update to assistive technology.
- Leaving the indicator visible after completion or failure.

## Sources

1. [Progress indicators](<https://developer.apple.com/design/human-interface-guidelines/progress-indicators>) — Apple · Institutional guideline
2. [ARIA: progressbar role](<https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Reference/Roles/progressbar_role>) — MDN Web Docs · Technical documentation

## Related topics

- [Loading State](<https://wiki.soroush.uk/topic/loading-state/>)
- [Skeleton Screen](<https://wiki.soroush.uk/topic/skeleton-screen/>)
- [Reduced Motion](<https://wiki.soroush.uk/topic/reduced-motion/>)
