Transient feedback shows a message briefly, then removes it without asking the actor to do anything. The usual delivery vehicle is a toast.
Two situations
Acknowledgement. The actor triggered the change and is watching for the confirmation.
Events from elsewhere. The same delivery also carries events the actor didn’t trigger — a collaborator joining, a background export finishing. Here, the actor might genuinely miss the message. That’s accepted as the tradeoff for not interrupting them. That only works if the actor doesn’t strictly need to know. If they do, the event also needs a durable home — e.g. an activity log entry — even when a toast announces it too. See notification pattern.
Timing
The dismissal interval resolves a tension between reassurance and intrusion. Short confirmations — file saved, item deleted — typically dismiss after 4–5 seconds. A message carrying an action needs longer: the actor must notice it, decide, and act. 8–10 seconds is a reasonable minimum when undo is offered.
Avoid very long durations. If the information needs to persist, the move is no longer transient — use a callout instead.
Carrying an action
A single inline action can ride along before the message dismisses. Undo is the canonical passenger: the act completes immediately, and the dismissal window is the recovery window. Anything more complex than one action belongs in a callout, or in a dialog if the actor must decide before continuing.
Resources & references
Related patterns
Instantiates
- Status feedback — the pushed, self-dismissing delivery shape of status feedback
Complements
- Undo — the dismissal window doubles as the recovery window — transient feedback is the primary carrier for undo affordances
Related
- Notification — the coordination pattern that selects delivery type and disruption level; its decision tree routes dismissible, non-actionable messages here