VOL. III · CH. 3.23 · COMPONENT
Notifications & Toasts
Brief, timely interruption — done right, it informs; done wrong, it becomes noise the user learns to ignore.
1 min read · 124 words
3.23.1Definition & Anatomy
A toast is a small, temporary message confirming an action or surfacing an update, typically auto-dismissing after a few seconds without blocking interaction — distinct from a modal (3.27), which demands a response.
3.23.2Common Mistakes
- Auto-dismissing before a user has had time to read longer messages.
- Stacking too many toasts simultaneously, overwhelming rather than informing.
- Using a toast for something that actually requires user action or acknowledgment.
3.23.3Best Practices
- Scale display duration to message length; never auto-dismiss critical errors without user acknowledgment.
- Limit simultaneous toasts and queue additional ones rather than stacking indefinitely.
Example"Changes saved" toasts confirm a background action without interrupting workflow — the defining reason toasts exist as a lighter-weight alternative to a modal confirmation.