Patterns
Loading, empty and error states
Each state has a different reason and a different next step. Write them deliberately.
Loading, shaped like the content
Long work, honest progress
Analyzing 1,001 samples
Fitting step response
Exporting report
No data yet
No runs for RW-05 yet
Runs appear when a bench finishes a test profile on this actuator.
No results
No runs match “R-09”
The Fail filter is on, and no failing run has that ID.
No permission
Bench 5 is restricted
Thermal chamber runs are visible to the thermal team. Maria Silva can grant access.
Error, with recovery
Traces could not be loaded
The sample store timed out. Nothing was lost; the run summary below is current.
2 of 8 runs are missing current data
The phase shunt was offline on Bench 1 on 16 Nov.
| State | Say | Offer |
|---|---|---|
| Loading (under 300 ms) | Nothing; show the content when ready | – |
| Loading (longer) | A skeleton shaped like the content, or a spinner with what is loading | Cancel, if it is long |
| No data yet | What will appear here | The action that creates the first item |
| No results | Which filter excluded everything | Clear the filter |
| No permission | Who can grant access | Request access |
| Error | What failed, in plain words; whether data was lost | Retry; a way to report it |
| Partial | What loaded and what did not | Retry the failed part |
Never show raw error codes or stack traces as the message. Never fake progress: use an indeterminate indicator when the duration is unknown.