"Github's Design System has banned toast messages. Toast messages are little messages that appear on top of the UI to give you feedback about an action you just took. Banning toast messages is an excellent decision because they're not accessible and have bad UX. Here's a few reasons why: (1) They disappear automatically after a few seconds - at best this is stressful, at worst you'll miss it (2) They obscure the content underneath which is frustrating and slows you down"
"It depends on the action. Sending an email is instant so there's no need for a toast message. But let's say you're exporting videos which take a long time. You don't want to stop users from working on other things. In this case, give users a clear message that the export has started and that the user will be notified when the export is ready to download. That notification might come via email or via the UI or both."
GitHub's Design System banned toast messages because they are inaccessible and produce poor user experience. Toasts commonly disappear automatically after a few seconds, which can create stress or cause users to miss feedback. Toasts obscure underlying content, frustrating users and slowing workflows. Small, edge-placed toasts are difficult to spot. For long-running tasks, the interface should clearly indicate that an export has started and promise notification when the output is ready, via email, the UI, or both. For quick actions like saving, provide immediate click feedback and ensure server responsiveness to avoid repeated user clicks.
Read at Adamsilver.io
Unable to calculate read time
Collection
[
|
...
]