Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

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 to improve the UX of an applicationour applications.

Empty states are moments in a user’s experience where there is no content to display. These moments can be utilised as opportunities to guide users and improve the UX of an application.

...

LUX has specific designs for 4 empty state types. In instances where an empty state should be shown on a full page empty state instances, the appropriate corresponding illustration should be used in place of page content. In instances where an empty state must should be shown within in a smaller content container, such as a widget, the corresponding icon should be used in place of the relevant illustrationinstead.

Type

Usage

Illustration

Full page

Widget

No results found

Use when a user’s search criteria returns no results.

No <entities> defined

Use when no entities, such as forms, have been added/defined.

Render the LUX frame, including the VerinTop.

Replace the full content area with the empty state.

You’re all caught up

Use when a user has no new notifications to review.

Render the LUX frame, including the VerinTop.

Replace the content pane area with the empty state.

Waiting

Use when an action is in progress.

Render the LUX frame, including the VerinTop.

Replace the full content area with the empty state.

...

  • 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

...