Brand Design System
CommunicationMaterial Design 3

Snackbar

Snackbars provide brief notifications about app processes at the bottom of the screen. They appear temporarily and disappear automatically without requiring user interaction.

Overview

Snackbars inform users of a process that an app has performed or will perform. They appear temporarily, towards the bottom of the screen. They should not interrupt the user experience, and they do not require user input to disappear. Snackbars can contain a single action that is optional and does not block the disappearance of the snackbar.

Live Preview

Item added to cart

Snackbar Variants

Single-line

Single-line snackbar message

Single-line with action

Message sent

Two-line

Unable to send photoRetry in 5 seconds

With close button

Notification settings updated

With leading icon

File uploaded successfully

Brand Properties

The following table shows all CRAFT Snackbar properties with their default values and brand-specific mappings.

PropertyTypeMaterial DefaultHoB ValueTAE Value
Background ColorColor picker#313033#1f2937#1f2937
Text ColorColor picker#F5F5F5#FFFFFF#FFFFFF
Action ColorColor picker#BB86FC#8B9F4A#5F982F
Border RadiusInput (px)4px8px8px
Font SizeDropdown14px14px14px
Font WeightDropdown400400400
Action Font WeightDropdown500600600
Padding VerticalInput (px)14px12px12px
Padding HorizontalInput (px)16px16px16px
DurationInput (ms)4000ms4000ms4000ms
Min WidthInput (px)288px280px280px
Max WidthInput (px)568px480px480px
PositionDropdownbottom-centerbottom-centerbottom-center
Margin BottomInput (px)24px16px16px
ShadowDropdownelevation-3mdmd

Positioning

Top Left
Top Center
Top Right
Bottom Left
Bottom Center (Default)
Bottom Right

Accessibility

  • Use role="alert" or role="status" for screen reader announcements
  • Action buttons must be keyboard accessible
  • Provide enough display time for users to read the message (minimum 4 seconds)
  • Do not use snackbars for critical information that requires acknowledgment
  • Ensure action text has sufficient contrast against the background
  • Consider users who may need more time to read and interact

Best Practices

Do

  • Keep messages brief and clear
  • Show only one snackbar at a time
  • Use for low-priority, non-blocking feedback
  • Provide an action when users can undo

Don't

  • Stack multiple snackbars
  • Use for critical errors that need acknowledgment
  • Include required actions users must take
  • Make snackbars persistent without user control

Related Components