Summary by TwinMind · 8m 55s
Summary by TwinMind · 8m 55s
The case against toasts
The case against toasts
Theo - t3․gg
Theo - t3․gg
Toast UX Problems Overview
- Core issue: toasts appear far from user's attention/action location
- Locality mismatch: action location ≠ feedback location
- Personal experience: prefer old P-thing version with inline loading states over current toast system
YouTube Toast Issues Analysis
- Multiple problems in save-to-playlist flow:
- Click save button (right side) → modal (center) → toast (bottom left)
- Delayed toast without loading indicator
- Must wait multiple seconds for previous toast to disappear before new confirmation
- Stacking toast problems when rapidly clicking actions
- Demonstration: save to playlist → remove → add to different playlist creates toast queue chaos
- Undo button in toast unnecessary (can just uncheck checkbox)
Better Solutions Proposed
- No toast approach: inline feedback at action location
- Loading spinners next to buttons being clicked
- Dropdown menus instead of modals
- Loading indicators that disappear when action completes
- Visual state changes imply success (e.g., email disappearing from list)
Email Client Examples
- Gmail: archive toast unnecessary since email disappears (visual confirmation)
- Superhuman:
- Has delayed send feature (5-10 second window)
- Auto-archives sent emails
- UX limitation: can't click toast to view sent email
- Only options: instant send or undo
- Missing: send + view email option
Personal Tool Analysis
- P-thing comparison:
- New version: toast in corner after copy action
- Old version: loading state directly under clicked element
- Old version felt more responsive despite being "objectively uglier"
- Sonner library makes toast implementation easy but doesn't solve core UX issue
Development Reality
- Sonner library: convenient promise-based toast API
- Easy loading/success/error states
- Heavily used in codebase for demos/tutorials
- Looks good but creates focus shift problems
- Better than nothing: toast preferable to no feedback at all
- Quick implementation: toast often chosen due to time constraints
Large Company UX Issues
- Trillion dollar companies ignore basic UX improvements
- Small improvements (0.1x) have massive ROI with billion+ users
- YouTube spam reporting example:
- Previously: 9 clicks per spam comment
- Process: report → modal → checkbox → next → confirm → next → hide user checkbox → confirm
- Solution implemented: bulk checkbox selection + one-click removal
- Took 3 months but dramatically improved creator experience
Toast Overuse Problem
- Overused as default feedback mechanism
- Stacking doesn't solve fundamental locality issue
- Pretty animations don't address core UX problems
- Need contextual feedback at action location instead
