There are two types of messages that differ by purpose and application:

  • Alert – a static message displayed on a particular page. It informs the user about the changes happening in the system independently from the user, for example, license expiration information, notification about new options or limitations, etc.
  • Toaster – a short non-modal message that notifies a user of the results of their action’s execution.

To show information about an error, it is possible to use either an alert or a toast. An alert should be used on modal windows – dialog windows and drawers. A toast should be used in non-modal cases.

Using toasts

Toasts should be used:

  • There is no way to show the user the results (or any kind of reaction or feedback) of the operation they are performing in the same area of the user interface that has the user’s attention focus.
  • A critical operation has just been completed, or an event has occurred that influences the operability and performance of the entire system or a web site or other users’ resources, etc. For example, the user is shown a toast when the user successfully removes an extension (can only be hidden manually).

Toasts should not be used:

  • A new object has been created – the correct way is to update the page and position the focus on the newly created object.
  • Confirmation of an action (deletion, saving, transition) that completes obviously, without the need to supplement it with a toast.

Note: Toasts are not substitute for validation.

Use discretion, do not show toasts for every user’s action.