4 ms·

I agree with post and don't like toasts either. The thing is, they don't solve a UX problem as much act as a catch-all solution for "respond to user action". I

• gorjusborg 2y ago
  It's hard to agree/disagree on UX without all the application and domain context, but I do feel like toasts are valuable when you are communicating information to the user that is not tied to a fixed UI location/time, but do not want to force interaction (like you do with a modal). I have seen modals used to communicate status and reaffirming information that does not require action, and between the two, toasts are a better fit. That said, you still need to be smart where the bar is in terms of what is worth communicating. None of us want applications to blather on about stuff we don't care about.
• samsolomon 2y ago
  Yeah, I'm not a huge fan of toasts. And I generally agree with the sentiment that it would be better to have indicators closer to where the action was taken. But, I'm not sure how else I would approach this? I think the main benefit is the catchall approach allows the team to focus on other customer problems. I lead the design system team for an enterprise SaaS company—there are so many controls across so many views. It's hard to imagine including a feedback mechanism like this in every component. And I still think we'd need some sort of toast confirmation for deleted records?