Feedback that does not block
McFarlane (2002) found immediate interruptions harm performance most, and Iqbal and Horvitz (2007) showed returning to tasks after alerts takes substantial time. Toasts deliver lightweight results such as 'Saved' or 'Moved to archive' without breaking flow. Material Design (Google, n.d.) calls them snackbars: one at a time, brief, near the bottom.
When to use and avoid
Because toasts vanish, they suit nothing users must read. Payment failures or data-loss warnings need a modal dialog or inline message. Pielot et al. (2014) show people already receive many notifications daily, and Mehrotra et al. (2016) found content and timing drive receptivity. Toasting every action trains users to ignore them; visible results like a like button need only a microinteraction.
Timing, placement and accessibility
Place toasts clear of bottom navigation and sticky buttons, extend duration for longer text and give enough time to hit actions like Undo. WCAG 2.2 (W3C, 2023) requires status messages to be announced without moving focus, using role="status" or aria-live. As Lazar et al. (2007) found, transient information is easily missed by screen-reader users; see web accessibility.
FAQ
- How long should a toast stay?
- Around four seconds or more for short text; longer with actions or long text, and allow manual dismissal if needed.
- Are toasts and snackbars different?
- Nearly the same; Material calls the version that can hold an action button a snackbar.
Sources reviewed: 2026-10-27
References
- Google. (n.d.). Snackbar. Material Design 3. Official rules for snackbar placement, duration and actions.
- Pielot, M., Church, K., & de Oliveira, R. (2014). An in-situ study of mobile phone notifications. In Proceedings of MobileHCI 2014 (pp. 233–242). ACM. Field study showing people receive dozens of notifications daily.
- Mehrotra, A., Pejovic, V., Vermeulen, J., Hendley, R., & Musolesi, M. (2016). My phone and me: Understanding people's receptivity to mobile notifications. In Proceedings of the 2016 CHI Conference on Human Factors in Computing Systems (pp. 1021–1032). ACM. Content and timing drive notification receptivity.
- McFarlane, D. C. (2002). Comparison of four primary methods for coordinating the interruption of people in human-computer interaction. Human–Computer Interaction, 17(1), 63–139. Compares immediate, negotiated, mediated and scheduled interruptions.
- Iqbal, S. T., & Horvitz, E. (2007). Disruption and recovery of computing tasks: Field study, analysis, and directions. In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (pp. 677–686). ACM. Shows the time cost of returning to tasks after alerts.
- World Wide Web Consortium. (2023). Web Content Accessibility Guidelines (WCAG) 2.2. Status messages (4.1.3) and timing adjustable (2.2.1) criteria.
- Lazar, J., Allen, A., Kleinman, J., & Malarkey, C. (2007). What frustrates screen reader users on the web: A study of 100 blind users. International Journal of Human–Computer Interaction, 22(3), 247–269. Surveys frustrations of 100 blind screen-reader users.
