Notifications provide an important layer of feedback for the user when interacting with Arc. Notifications can communicate system status, capture errors, and keep users on track during important workflows. Arc utilizes three different components for notifications across the system (listed in order of increasing urgency): Criteria for choosing the right notification component include:
- Inclusion of an action
- Type of information being communicated
- Duration on screen (transient, dismissible, or both)
- Transient - Automatically dismissed after a period of time
- Persistent/Dismissible - Dismissed after user input
When consecutive alert updates are necessary (or if prior alerts have not been manually dismissed), they should stack up to a maximum of 3 alerts. The newest alert will always appear from the bottom, pushing the older alerts vertically upwards. The oldest alert in the series should automatically dismiss to make room for newer alert updates.
When consecutive snackbar updates are necessary, they should appear one at a time and cycle automatically. If there is an alert stack present, snackbars should always push the entire stack vertically upwards before cycling. Snackbars should not affect any rules in place around consecutive alerts.