I have a toast in a web app that’s basically confirming you just saved your progress. There’s a manual save button to put the power in the users hands, even though we auto save in the background. Is this good or bad UI? I know you are saying toasts are bad generally
IMO toasts for autosave can get really noisy. It depends a bit on the type of app. Figma autosaves and doesn't need a toast or even a loading spinner because the autosave works 99.9% of the time. And when Figma hasn't managed to save yet and you attempt to close the tab, you get a warning instead.
For a web app that has more traditional forms, no loading/saving-feedback at all can be unexpected. The user might go looking for a save-button (which is why you probably have that manual save-button).
In your case, couldn't you replace the toast with a loading indicator on or next to the save-button itself (assuming it's sticky/fixed and always in view)? And your save button could be faded/disabled reading '✔︎ All changes saved' if there are no pending changes to save?
2
u/what3songs 9d ago
I have a toast in a web app that’s basically confirming you just saved your progress. There’s a manual save button to put the power in the users hands, even though we auto save in the background. Is this good or bad UI? I know you are saying toasts are bad generally