[jmercouris]

Toasts are a great way to lose information. They are a terrible design and should not be used. They distract the user, are not dense with information, and provide no value. If a message is important enough for the user to read, it should be a dialog box.

[jopicornell]

Dialogs are a great way to lose information. They are often dismissed by users that want to do their job and are interrupted by modals. Users focused on their tasks blindly dismiss dialogs.

Read the above as a critique to your strong opinion and not an opinion of mine.

My opinion is that toasts are great for notifications that can be reviewed/checked later, like chat notifications or finished background tasks.

What should be avoided, just for the same reason as modals/dialogs, is an overuse, causing fatigue.

[mhitza]

Dialogs don't have to be modal, and in the parent comments context they aren't.

[oulipo2]

Most of the time they're used for a quick visual confirmation that "your operation went right"

[jmercouris]

The information that the user did something "right" should be responsive next to where the user initiated the action- not in a random corner.

[tyre]

That’s why confetti exists

[ahallock]

Developers reach for Toasts because they're zero effort. Good user experience takes a lot of thought and you can skip all that with Toasts haha.

[robin_reala]

Zero effort, and they animate. Components that have animation baked in are drug-like in how they hook in designers and devs who are only thinking about the visual presentation.

[wildrhythms]

Zero effort, and it's basically a crude visualization of a good old message bus :P