โ€‹โ€‹โ€‹๐Ÿ„โ€‹Snackbars

โ€‹
โ€‹Definition

โ€‹โ€‹Provide brief messages about application processes with a CTA. There's ALWAYS an action for a user in a snackbar. 

โ€‹
โ€‹Visual Examples

โ€‹โ€‹

โ€‹
โ€‹Usage

  • โ€‹โ€‹Informs user of a process that an app has performed or will perform
  • โ€‹โ€‹Should not interrupt experience
  • โ€‹โ€‹Can stack

โ€‹
โ€‹Principles

โ€‹โ€‹Informational: provides updates on app process
โ€‹โ€‹Feedback: gives users feedback in response to actions they take
โ€‹โ€‹Interactive: allows for user interactions to dismiss or take further action

โ€‹
โ€‹Types

โ€‹โ€‹Similar to a toast, but more versatile and customizable with actions and interactive by nature

โ€‹
โ€‹Priority

โ€‹
โ€‹Low/Non-critical

โ€‹
โ€‹Behavior

  • โ€‹โ€‹Appear sticky at the bottom of the page
  • โ€‹โ€‹Actions for users to take

โ€‹
โ€‹Atomic Model Identification

โ€‹โ€‹Organism (can be placed without other UI elements)

โ€‹
โ€‹Recommendations

  • โ€‹โ€‹Snackbars should be used when there are actions available
  • โ€‹โ€‹Ex. "Report generated, click to view." "Ticket needs your attention, click to view."
  • โ€‹โ€‹Contain actions and a close button
  • โ€‹โ€‹Interactive and persist until action taken
  • โ€‹โ€‹Appear at the bottom of the screen 

โ€‹
โ€‹Dos and Don'ts

โ€‹
โ€‹Do
โ€‹โ€‹Use elevation and a dark background so that snackbars are easily identified.
โ€‹โ€‹
โ€‹
โ€‹Don't
โ€‹โ€‹Do not alter the shape of the snackbar container.

โ€‹
โ€‹Content

  • โ€‹โ€‹Content
  • โ€‹โ€‹Content
  • โ€‹โ€‹Content

โ€‹
โ€‹Accessibility Requirements & Resources

  1. โ€‹โ€‹Toasts should not acquire keyboard focus upon appearing.
  1. โ€‹โ€‹Toasts should not contain long messages since they disappear automatically.
  1. โ€‹โ€‹Screen readers do not interact with toasts, but can interact with snackbar actions.

โ€‹
โ€‹Mountaineer Design System Link

โ€‹
โ€‹Related Components

  • โ€‹โ€‹โ€‹+mushroomToastsโ€‹ 
  • โ€‹โ€‹โ€‹+artist paletteIconsโ€‹ 
โ€‹โ€‹
โ€‹โ€‹