Toast and snackbar
A toast or snackbar reports what just happened in a short message that leaves on its own and does not block the screen. Material 3 calls it a snackbar and can add one action; iOS has no system toast.
Why it matters
A toast confirms what happened without stopping the person. Because it leaves on its own, it cannot carry anything that must be read.
On iOS there is no system toast, so a shared design has to draw its own.
Toast and snackbar on iOS and Android
Also called Snackbar vs toast. The same idea in each system, with the values Appetite UI gives it.
| Value | iOS | Android | Appetite UI |
|---|---|---|---|
| Name | No system component | Snackbar | Toast |
| Component | iOS | Material 3 | What differs |
|---|---|---|---|
| Snackbar | No counterpart | M3 / Snackbar, 344 wide | The Apple pages have no snackbar |
In practice
A message that needs a decision is an alert, not a toast. A snackbar may carry one action, usually Undo.
Appetite UI draws it as Toast, and the Material set carries Snackbar at 344 wide with text only, text and action, and a longer action.
Common mistakes
- Reporting a critical error in a toast that disappears. Use an alert.
- Adding more than one action. A snackbar takes one, usually Undo.
- Covering the tab bar or the floating action button.
Questions
What is the difference between a snackbar and a toast?
Both show a short message that disappears on its own. A Material 3 snackbar sits at the bottom and can carry one action, such as Undo; toast is the general name, from Android’s older Toast, for a message with no action.
Does iOS have a toast?
No. iOS has no system toast; apps draw their own or use a banner. Appetite UI’s Toast covers both platforms, with two types and five states.
Sources
The pages the facts above rest on, each read October 31, 2026.