Separating Messages from the Notifications Pattern

[thefirstartist]

Summary

The current Notifications pattern in Carbon includes both banner and toast notifications. However, banners are primarily used as contextual messages to inform users about specific use cases, such as errors, warning, or information, and do not function as true notifications. This conflation creates confusion and diminishes clarity in both design and user experience. I propose separating banners into a distinct Messages pattern, ensuring that notifications are reserved exclusively for transient, action-oriented alerts. This change will enhance usability, reduce cognitive load, and provide clearer guidance for designers and developers.

Relevant information

Banners are messages, not notifications:

Banners are primarily used to inform users about specific use cases, such as errors, warnings, or general information. These messages are often persistent and contextually tied to a particular form or action. They don't fit the definition of a "notification," which implies an alert designed to capture attention, often transient and possibly unrelated to the immediate context.

An inline banner is a message, not a notification.

Notifications signal system alerts

Notifications, primarily in the form of toasts, are designed to alert users to system events or updates. For example, a notification might inform users that they are running out of storage space or that the system will be automatically updated to a new version tonight. While some notifications may require immediate user attention or action, they are typically global or system-level. In contrast, messages are contextual and specific to the form or component the user is currently interacting with.

Notifications panel

Notifications should automatically dismiss after a few seconds to minimize distractions. However, they should also be saved in the notification panel or notification center for users who need more time to read them or wish to revisit them later. In contrast, messages are task-generated, require immediate user engagement, and are not saved.

Conclusion

Separating messages from the notifications pattern in the IBM Carbon Design System will improve clarity, usability, and design consistency. Notifications, as global or system-level alerts, should remain transient and accessible in a notification panel, while messages, as contextual and task-specific elements, should focus on immediate user engagement without being saved.

[thefirstartist]

@benjamin-kurien @oliviaflory Please let me know your thoughts. Thanks!