Some of the designers and frontend devs I’ve worked with may remember my rants against toast notifications:
“Why do I need a success message for every action? I expect things to work. Only tell me when something breaks.”
But… I’ll admit it: Sometimes toasts do have their merit.
Two examples from poketto.me:
🔹 Copy to clipboard (Podcast feed URL):
When users click the “copy” button, the action happens instantly. But without any feedback, it feels… awkward.
Did it work? Was the button even clickable?
A quick toast (2–3 seconds) saying “Copied to clipboard” removes the doubt and feels just right.
🔹 Adding a Save to a podcast feed:
This is more complex. A Save might: Exceed the user’s monthly TTS quota, trigger auto-purging of older episodes, and take several minutes to process. Users need feedback now, but also more detailed info.
My current solution: Show a brief toast confirming the Save will be added (2s timeout) Then, follow it up with a second toast that contains detailed info (ETA, limits, etc.). That one doesn’t auto-dismiss, so users can read it at their own pace.