Description
Empty states are moments in a user’s experience where there is no content to display. These moments can be utilised as opportunities to communicate system status, expose new features and provide pathways relevant to a user’s workflow.
Types
LUX has specific designs for 4 empty state types. In instances where a single empty state should be displayed, use the relevant illustration. In instances where there are several content areas, or multiple empty states need to be shown at the same time, use the corresponding icon(s) instead.
Type | Usage | Illustration | Icon |
|---|---|---|---|
No results found | Use when a user’s search criteria returns no results. |  |  |
No <items> defined | Use when no items, such as users in a list of users, have been defined. |  | |
Empty notifications | Use when a user has no new notifications to review. |  | N/A |
Waiting | Use when an action is in progress. |  | Discuss with Asaf |
Usage & Behaviour
General guidelines
Structure
An empty state consists of:
An illustration - which visualises and contextualises the current state of the application.
Message - describes the state the application is in to the user. Should be brief and informative.
Call-to-action button - a contextual action/UI element relevant to the user’s task. (Optional)
Text link - a contextual action/UI element relevant to the user’s task. (Optional)
For example:
Placement and Positioning
Empty states should replace the content that would ordinarily be shown.
Empty states should be centered horizontally in the content area.
Content
Empty states can be used to display a wide variety of content. See examples above. - Carliefy
Use an accurate explanation that details the state the application is currently in.
Use contextual cues relevant to the user’s task. Where relevant, include direct links to the steps that need to be taken in the user’s workflow to accomplish a task.
Interaction
Empty states are mostly non-interactive, with the exception of action options such as text links and call-to-action buttons. For component-specific interactions see the documentation of that component.
When an empty state is embedded in a container, the rest of the application should remain interactive.
Best Practices
Use:
When content does not yet exist for a screen or pane to provide guidance on how to populate the area with that content.
Contextual prompts (i.e., text links) that help users with getting started on key tasks.
Clear, concise written explanations.
Neutral illustrations that are representative of the state, reduce stress and add aesthetic appeal to the interface.
Don’t use:
Totally empty states, this approach creates confusion for users.
Inaccurate written explanations.
Irrelevant actions.
Unrelated visual content.
General
<…>
Accessibility Compliance
Unless otherwise specified, see our general compliance information in Fundamentals - Accessibility
Responsive design
Verint products should dynamically respond to the user’s screen size, platform, and orientation, supporting all devices down to the common tablet size (960px width).
Design
Zeplin link | Screen thumbnail |
|---|---|
 |
Code
