> The users almost never saw them and when they did they didn't see them long enough to be able to communicate what the message said, often trying to paraphrase.
Theres an art to writing terse copy for the toast, and picking durations that make sense. I think this is likely more a poor application of the pattern rather than the pattern itself being bad.
It’s extremely easy to get the “art” wrong. In my case, I didn’t always know what the errors were because they were returned from 3rd party API’s and many of them the application had never seen before. If there were a proper log somewhere, maybe, but toasts are very easy to use poorly.
