The use case for snackbars (brief, timely, non-critical and non-interruptive messaging with an optional single message) and dialogues (interruptive messaging for critical messages) I think is fairly clear. A banner would fall somewhere in between in that it has a higher level of priority and cognitive complexity (ie, multiple options) than a snackbar, but a decision or interaction isn't strictly necessary to block the usage of the interface otherwise.
Obviously, it would be great if we could use snackbars 100% of the time (pending potential accessibility issues) but that's likely not going to be the case. I'd start here by introducing a snackbar component, and then adding more components as projects have a need for them.
There are a number of different, but closely related components we might want to consider making available:
The use case for snackbars (brief, timely, non-critical and non-interruptive messaging with an optional single message) and dialogues (interruptive messaging for critical messages) I think is fairly clear. A banner would fall somewhere in between in that it has a higher level of priority and cognitive complexity (ie, multiple options) than a snackbar, but a decision or interaction isn't strictly necessary to block the usage of the interface otherwise.
Obviously, it would be great if we could use snackbars 100% of the time (pending potential accessibility issues) but that's likely not going to be the case. I'd start here by introducing a snackbar component, and then adding more components as projects have a need for them.