Skip to content
Ben Serkan Zararsız

Not every message needs a modal

Toast, banner, sheet or alert? Most products get this wrong in both directions: they interrupt for nothing and whisper when it matters. A field guide to interruptions, with demos.

On this page
  1. Intro
  2. Match the weight
  3. Toasts are for things that may be missed
  4. Alerts are for consequences
  5. Sheets are for small tasks
  6. The ladder

Every week I see the same two mistakes, often in the same product. A modal that congratulates you for saving a draft. And an error that fades away at the bottom of the screen before anyone has read it. One interrupts for nothing. The other whispers when it should speak up.

The fix is one simple idea: the weight of the message decides the weight of the component. This is the ladder I use in every project, from quietest to loudest, and when each rung is right.

Match the weight

Feedback should match the significance of what it says. Status can sit passively in the interface, where people find it when they want it. A warning about lost data has to interrupt. Everything in between has a place on the ladder: indicator, inline message, toast, banner, sheet, alert. The mistake is picking a rung by habit instead of by consequence.

One question sorts most cases: what happens if the person does not see this? If the answer is “nothing”, it is an indicator or a toast. If the answer is “they lose work or money”, it is an alert. Most messages are far closer to nothing than teams think, and people quickly learn to click past a product that cries wolf.

Profile

A quiet status next to the action

Profile
Success!

Your changes have been saved successfully.

A modal to confirm what you just did

Toasts are for things that may be missed

A toast is a small, quiet confirmation that disappears on its own. That is its strength and its limit. Right for “saved”, “copied”, “sent”, wrong for anything the person must act on. Shown as a toast, an error fades before anyone reads it, and people keep waiting for a page that has already failed. Errors belong next to the thing that failed, and they stay until the problem is solved.

Two details make toasts bearable. The timer pauses while the pointer rests on it, and while the tab is hidden. Nobody should lose a message because they looked away for a moment.

Checkout
Please add a domain, like serkan@example.com

Inline, next to the field, stays until fixed

Checkout
Something went wrong.

A toast at the bottom, gone in three seconds

Alerts are for consequences

An alert stops everything. That is a cost, and it is only worth paying when the person is about to lose something they cannot get back. Even then the alert has to earn its reading: a title that says what will happen in plain words, and buttons that name the action. “Delete project” beats “OK”.

The reverse matters just as much. Do not alert for common, reversible actions. Nobody needs a confirmation for every deleted email. Delete it, offer a short undo, and move on. Interfaces that ask “are you sure?” all day train people to click through without reading, so the one alert that matters gets ignored too.

Inbox
Invoice #2041
Weekly report
Lunch on Friday?
Deleted “Invoice #2041”

Delete at once, offer undo

Inbox
Invoice #2041
Weekly report
Lunch on Friday?
Are you sure?

Do you really want to delete this message? This action cannot be undone.

Confirm every single time

Sheets are for small tasks

Some messages are really tasks: pick a date, attach a file, choose a location. That is a sheet, not an alert. On the phone it rises from the bottom, it can be dragged away, and it keeps the parent view in sight so people never lose their place. One sheet at a time, always a way to cancel, and never a second sheet on top of the first.

If the task grows, the sheet is the wrong container. A multistep task deserves the full screen or its own page. A modal that starts to feel like an app inside the app is a sign that the design has lost its way.

Trip to Zurich

Fri 20 Nov · 2 travellers

Add a return date to see prices.

Return date

Rises from the edge, parent stays visible

Trip to Zurich

Fri 20 Nov · 2 travellers

Add a return date to see prices.

Return date

Floats in the middle, tiny close target

The ladder

From quietest to loudest:

  1. Indicator: a badge, a dot, a changed icon. For status people check when they want to.
  2. Inline message: next to the field or the item. For validation and anything that must be fixed.
  3. Toast: a short confirmation that can be missed without harm.
  4. Banner: a persistent notice for the whole page, with a way to dismiss it.
  5. Sheet: a small task that returns to the parent view.
  6. Alert: a consequence the person cannot undo. Rare, and worth every pixel.

Pick the quietest rung that still does the job. Your product will feel calmer, and the one time you do interrupt, people will listen.

Sources

  1. Apple Human Interface Guidelines: Alerts
  2. Apple Human Interface Guidelines: Sheets
  3. Nielsen Norman Group: Indicators, Validations, and Notifications: Pick the Correct Communication Option (2024)
  4. Nielsen Norman Group: Modal and Nonmodal Dialogs: When (and When Not) to Use Them (2017)