Define Error and notification patterns

[aweell]

Effort

Providing a coherent error and notification display across a diverse set of applications is an important milestone in the chase of a better user experience. To accomplish this task, we need to move from the component level behavior to define how the application will behave when something unexpected happens or we need to provide feedback to the users.

• Research the ways our current applications handle this behavior.
• Standardize different solutions that can be applied.
• Design and document when and how error and feedback notifications should appear, and how to effectively communicate task or application status.
• Design and document the distinct types of notifications that we will provide alongside the duration in screen, position, usage, and accessibility.

Impact

Product teams: Have a set of guidelines providing guidance about how to handle the different feedback processes during the application usage (when and how to show a modal/inline alert, positive feedback, toasts, badges, etc...).

End customer: Improvement in the user experience by receiving consistent feedback on the task/application status.

[github-actions[bot]]

This issue is stale because it has been open for 15 days with no activity. If there are no further updates or modifications within the next 15 days, it will be automatically closed.

[github-actions[bot]]

This issue is stale because it has been open for 15 days with no activity. If there are no further updates or modifications within the next 15 days, it will be automatically closed.