Design Notification Systems Based on Importance
Feedback & States · notifications
Updated 2026-07-28
- Treat notifications as a system, not isolated messages. The surface you choose determines how much attention the user gives, so match the notification type to the urgency of the information.
- Choose the right notification pattern for the situation:
- Use toasts for temporary, low-interruption updates that users can briefly notice and continue working.
- Use banners for important information that affects the broader experience and should remain visible.
- Use modals only for critical decisions that require user action before they continue.
- Use badges for passive reminders that users can address when they choose.
- Match severity to the notification surface:
- A new message → toast.
- A service disruption or degraded system → banner.
- A payment failure requiring action → modal.
- Unread activity counts → badge.
- Design each notification type with the correct behavior:
- Toasts should disappear automatically after a short period. For destructive actions, include an Undo option so users can recover quickly.
- Banners should remain until the user dismisses them or the issue is resolved.
- Modals should require a decision before the user can continue.
- Badges should remain quietly visible until the underlying item is handled.
- Manage multiple notifications carefully. Several toasts can stack with spacing and clear ordering. Multiple blocking modals create confusion and should be avoided.
- Do not choose notification surfaces out of habit. The wrong surface reduces attention, increases frustration, and can make important information easy to ignore.
- A strong notification system creates a clear relationship between urgency, interruption, and user action.
Related guides
UX Handbook