pattern-library 3 linked patterns checked
Carbon Design System Empty States Pattern
Distinguishes no-data, user-action, and error-management empty states, including no-results feedback after search and filter actions.
Read with a purpose
What this source can teach
Use this source to compare a documented solution with the task and states in your own product.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Dead-end empty state | Flag dead-end empty state when a blank area lacks a specific object name, cause, and reachable next action. | A blank or actionless content region is not a valid terminal state. | Carbon distinguishes no-data, user-action no-results, and error-management empty states, which helps diagnose dead-end blanks. |
| Empty state | Choose empty state only after the system knows the area is legitimately empty rather than loading, filtered, or failed. | The empty state identifies what is absent and why the absence is expected. | Carbon distinguishes no-data, user-action no-results, and error-management empty states and describes matching the state to cause. |
| No-results recovery | Choose no-results recovery whenever search or filters can produce an empty set. | The UI must explain that no matches were found and identify the active constraints. | Carbon distinguishes user-action empty states such as no search results from first-use empty states and system issue states. |
Comparisons supported by this source
- Dead-end empty state vs empty state vs no-results recovery vs error state
Carbon distinguishes no-data, user-action no-results, and error-management states.
- Empty state vs no-results recovery vs error state
Carbon distinguishes no-data empty states, user-action no-results states, and error-management empty states.
- Loading skeleton vs empty state vs error state
Carbon distinguishes no-data empty states from user-action and error-management states.
Evidence Role
This source is treated as pattern-library evidence. Its value comes from the specific claims and setting described above.
Publisher: IBM Carbon Design System. Last checked: .