A Plea for Better Software: Provide Auto-Save
Jens Meiert, June 25, 2007 / March 7, 2008.
This entry is filed under Usability, User Experience.
Applications do rarely automatically and/or periodically save users’ work and thus fail to prevent unnecessary, frustrating, and expensive work and information losses. Since this isn’t just a but a critical problem, we need to encourage application developers or their “masterminds”, respectively, to change that.
Basically, I could stop writing now, but I may add some trivia:
-
While the problem’s surely much older, I may cite Bruce Tognazzini’s (excellent) article on interaction design (2004?):
Ensure that users never lose their work as a result of error on their part, the vagaries of Internet transmission, or any other reason other than the completely unavoidable, such as sudden loss of power to the client computer.
(Even here, it has become completely inexcusable that today’s computers and operating systems do not support and encourage continuous-save. That, coupled with a small amount of power-protected memory could eliminate the embarrassment of $ 5,000 machines offering the reliability of 10-cent toys.)
-
Apple appears to have incorporated auto-save many years ago, and so did several Mac OS software producers. Although on that system, auto-save is relatively broadly supported now (system settings, for example, are saved without requiring you to push “Save” or whatever), some applications (like TextEdit) leave you out in the rain once “it” happens.
-
My favorite IDE IDEA (available on all major systems) knows auto-save for at least five years, if not since its creation. This is one of the reasons why I love it so much – I never lost my work (unless I decided to search through several GB data for idiotic regular expressions).
Figure: File menu with never needed “Save All” button.
-
Google and Mozilla are two other great examples for auto-save in action: While Google integrates auto-save in several web applications (like Google Reader) for quite a while now, the Mozilla Foundation added sort of “emergency save” functionality once e.g. Firefox crashes – next time you open the browser, you may restore the last session. This is great and exactly what we need in more applications.
So this became another guerrilla post nonetheless, but it should be obvious that we (would) all benefit from continuous-save. So when there’s a web app that might use some auto-save magic, let’s add it. And when there’s an (important) application that might use some work protection mechanism, let’s request and demand it (by contacting Microsoft concerning Office, for example).
Your experiences and thoughts?
Read More
Enjoy the most popular posts, probably including:
Comments
-
On June 25, 18:17 CEST, Eric said:
That’s something which irritated me when I switched to a mac: no apply and save buttons in preferences. I use Textmate a lot which saves your files when switching to another window which is quite good.
-
On June 25, 18:19 CEST, Jens Meiert said:
Irritated – and then pleased, right? (That’s why I tagged it “User Experience”, too, apart from the negative feelings an application or system crash causes …)
-
On June 25, 19:08 CEST, Duluoz said:
Every now and then, out of curiosity, I’ll try out new versions of design software such as Corel Draw. Corel’s products have had auto-save for years. You can also customize the frequency of saving if you like. However, I and many others have had this feature crash the application when triggered! How wonderful and counter productive is that!? Hahaha.
-
On June 26, 12:28 CEST, Jens Meiert said:
Now that’s great – there must be a reason why I never used Corel products yet
