|
My English is not very good. I just wanna ask, what would be the right success message? In my case, when the the user deleted a record, I'm thinking of what to display with these options:
Any suggestions or other ideas? |
|||||
|
|
In many cases the best message is no message ;) Is there the expectation of success? In these cases the only time a user wants to see a message is when something's gone wrong. Take file deletion in Windows. After the "Are you sure?" question has been answered there's no further message unless the file couldn't be deleted for some reason. Is there any other feedback that the record has been deleted? Taking Windows as an example again, the user can see that the file has been deleted as it no longer appears in the file explorer. Does the delete operation take a long time? If you're deleting something from a remote database there may be some time from when the delete request is issued and when the delete actually occurs. There's also a disconnection from the action and the result as the delete is asynchronous. In this case you probably do want a message. As to what that message should be, any of the ones you list are OK. However, you might want to drop the "successfully" as that raises the possibility of failure in the user's mind. The simple:
where |
|||||||||||
|
|
Is record the word the user understands? It sounds a bit database related - is it really speaking to the user in the language they understand - the 'user model'? If so Record deleted successfully is good. If not - replace the word record by the 'thing' the user understands. |
|||||||||||||
|
|
The word "successfully" means that there is an opposite situation and this situation happens very often and it was the Lucky case when it was done successfully: it was a lucky day for both of us (user and application). :) |
|||
|
|
|
I agree that no message would probably be the best way to communicate success. What is the right success message? Perhaps what you need is not a message but a hint that some thing has happened. For instance when I click on the text box to start typing this answer the border changed colour. That was enough to let me know that I was successful in selecting the text entry box. Similar hints which are unobstructive and don't take my focus away from the task I am trying to do. If you want to show that some thing was deleted, having a record count in a corner some where the animates as it decrease its count could be enough to let a user know that some thing was successful. Or more simply, having the item highlighted and change colour when you delete it could be enough. You just need to have some feed back that does not require the user to turn the focus away from what they were doing. It also should not be flashy and distracting. |
|||
|
|
|
Assuming you need to have the message at all (which you very well may not), I'd suggest one further clarification ... Instead of "Product removed" (or deleted), include an identifier for which product -- e.g. "Product 'xyz' removed." |
|||
|
|
|
It really depends on the situation. If the user is viewing their basket, they click remove and the item visibly disappears then no message would be required. However if the user is in a CMS system with hundreds of records a message such as 'Product removed' would be best. |
|||
|
|
