Feedback - action needs reaction

Alerts are rather discreet. The information they contain is more of a tip or hint, but not required to complete a task. They also fit well into the layout of the page, which is one of the biggest advantages of this feedback type. Alerts can always be displayed at exactly the point where the user is currently taking action. The component in which the alert is or appears changes little or not at all. This means that the user is not interrupted in his or her workflow.
Attention: In case an alert is displayed after an action has been performed, it should be in the user's view. If necessary, the scroll position must be adjusted.

Signs for the use of alerts:

• The layout of the page should remain the same so that the user does not get lost.
• It is rather additional information that is not absolutely necessary to finish a task.
• The initial state of a section where items can optionally be added by the user.
• You want to present information in more detail and more prominent than in a tooltip.

ESIs interrupt the user's workflow and attract a lot of attention. An ESI can fit into the layout of the page, but in some cases it can also overwrite the entire layout of the page. It is therefore especially important that they clearly signal to the user what is happening, why it is happening and what the next action is. The great advantage of ESIs is that frustrations or errors can be mitigated. Furthermore, the user is motivated to take action and it is always a good opportunity to enhance the user experience.

Signs for the use of ESI:

• There is nothing to display. Either by restrictions in the search/ filtering, or simply because there are no items yet.
• The missing content is essential for the successful completion of the user's task.
• You want to draw attention to an object.
• A message that is disappointing for the user should be "nicely wrapped".

A growl notification is very noticeable, but barely interrupts the user's workflow. On the one hand, because the lifecycle of a growl is limited and it disappears even without any user action, and on the other hand because the layout of the page is not affected. This is also the biggest advantage of growls. Their independence from the current view. So if the view changes or a modal is closed, growls are the right choice.

Signs for the use of growls:

• A general message is sent from the platform, which cannot be assigned to any element on the page.
• If the view changes after the completion of an action (e.g. by scrolling, closing a modal, navigation back or the like).

Modals are quite diverse and are in turn used in various areas. One of these areas is as feedback for the user. The modal interrupts the user's workflow the most and should therefore only be used with caution. As long as no decision has been made, the modal remains open and thus "forces" the user to take an action. The user must therefore conciously deal with the feedback and make a decision.

Signs for the use of modals:

• There is an information that is so important that the user must see it.
• In the case of a destructive action, to make sure that the user has not accidentally taken an action that he might regret later. Two of the most common cases where data can be lost are:
  1. The user clicks the delete button. (Attention: We distinguish between delete (gone for good use modal) and remove (can be easily recovered)
  2. The user has unsaved data in a form and navigates somewhere else or tries to reload the page