Comment by hinkley
7 years ago
So I should never pretend that an operation that took 10 ms took 200ms so the users stop hammering the Save button over and over again because there's 'no way' it could have saved that quickly?
7 years ago
So I should never pretend that an operation that took 10 ms took 200ms so the users stop hammering the Save button over and over again because there's 'no way' it could have saved that quickly?
Why wouldn't you instead show a timestamp of the last save, giving confirmation that the save really went through?
Or a quick tooltip that flashes "Document saved" before disappearing?
Or disable the button for a second after saved?
Or show a cute little "save complete" icon?
Or autosave on change and disregard the save button entirely?
Or just give a save button because that’s what people expect and want?
Our software product eventually got auto-save after having required manually saving for a while. We got rid of the save button, and got tons of complaints.
The button went back up, with no functionality, because users liked that.
Finally got rid of the button and put some text that said 'saving...' -> 'auto-saved' in its place.
Should have put "Saving. Please do not remove the MEMORY CARD™ or turn off the power."
Why not an enable/disable edit button?
Typically, applications disable the save button when there are no changes that could be saved.