Hacker News new | ask | show | jobs
by Mackser 670 days ago
I haven't heard many developers/designers talk about the overused practice of using toasts for UI feedback.

The post shares a few real-world examples and illustrates some of the problems with how they use toasts.

What do you think? Are toasts overused? In which cases do you use them in your own apps?

3 comments

I'd speculate that their overuse comes from convenience of displaying any message by throwing in a `showToast("Foo!")` opposed to altering each UI component to show the relevant feedback.
That cuts both ways IMO. At least with a toast system I know where feedback appear on a per app basis (or website or whatever). Imagine if every screen, view, list entry, checkbox had its own way of displaying feedback. It would be an enormous amount of overhead.
Toasts should be used if there is no direct relation to or interaction with a visible UI element: notification, heavily asynchronous processes, out-of-view modifications.
> Are toasts overused?

I think so, yes.

> In which cases do you use them in your own apps?

I don't. But I don't write mobile apps (where they make more sense) for distribution, so they don't address any need my applications have.