Is it good practice or not to give the user a notification of a successfully performed action? Like saving or deleting an item. Is it annoying and excessive or is it useful?

I am mostly referring to a toast notification, i.e. an auto-expiring notification

3 Answers 3


It is best to give some sort of feedback. The Netflix DVD Queue doesn't pop anything up, but it gives clear visual feedback that something has happened and that you can undo it. Netflix Queue Feedback

Gmail provides an actual popup, but it's completely ignorable. enter image description here

The problem with modal popup notifications is that stopping what you're doing in order to close notifications - that's what's "annoying and excessive."

So yes, provide feedback. And no, don't require users to close the notification.


Yes it is the best practice to show feedback messages on such actions... it means your system is having conversation with the user and the user is aware of what is happening, but don't annoy with too many alerts.

With a feedback cycle, you can tell the user what is going on in your application. However, keep in mind that the applications’s feedback should not be too annoying. Remember Microsoft’s Office Assistant “Clippy the paperclip” used in previous Microsoft Office versions giving you suggestions all the time? Feedback should have an additional benefit for the user and not distract him. With meaningless or too much feedback you will make the user experience worse – so use it wisely.



enter image description here

enter image description here

  • Ah, I see what you mean :) But what is "too many alerts"? How easy is it to annoy him? I have a graph where the user are able to add, delete, edit and copy different element. My guess is that he will probably perform more than one action each time he enters the web application. Each action is saved as it is performed.
    – efrethe
    May 31, 2016 at 12:02
  • @tessfred now it is more clear... Show the feedback inline with the component the user is modifying/saving... check the edit.
    – Diego
    Jun 1, 2016 at 3:29

Based on the comment you made to Diego, your question is a lot different than what it looks at first sight.

If you require a lot of interaction, then don't offer a notification each time, and don't save each action immediately.

Instead, create sessions where the user can do any amount of actions (you can autosave every X amount of minutes). In these sessions, allow to undo everything, and for each action performed use a subtle animation/transition so the user understand something happened. This information transmitted by the transition should be enough to convey the message.

After the user is happy with the changes, offer to save the changes as in any other app, and then display a "your changes have been saved" message.

By doing this, you won't overwhelm your users, you'll keep then informed of their interactions and you'll have one and only one notice for what is a single process (content edition).

Taking the Gmail example by Ken Mohnkern : just imagine if every time you perform an action when creating an email (editing, deleting, changing fonts, etc) you get a message. You'd be alienated in no time. Instead, all those actions are just subsets of the main action: send a mail. Thus, you get the message only when you send a mail or create a draft, not every time you perform an action.

In short

Use messages sparingly, and always try to define what the main action is, paying special attention to destructive actions

Additional References

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.