A Plea for Better Software: Provide Auto-Save

Published on Jun 25, 2007 (updated Jul 25, 2021), filed under development, design. (Share this post, e.g., on Mastodon.)

So far, applications rarely automatically and periodically save users’ work. They therefore fail to prevent unnecessary, frustrating, expensive loss of work and information. Since this isn’t just a but a critical problem, we need to encourage application vendors and developers to change that. More:

• 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.

  ([…] 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 Mac OS, auto-save is relatively broadly supported now (system settings, for example, are saved without requiring you to hit “Save”), some applications (like TextEdit) leave you out in the rain once they crash.

• My favorite IDE IntelliJ IDEA knows auto-save for at least five years, if not since its inception. This is one of the reasons why I love it so much—I’ve never lost my work with it (unless I decided to search through several GB of data using half-baked regular expressions).

  

• Google and Mozilla are two other great examples for auto-save in action: While Google has integrated auto-save in several web applications (like Google Reader) for a while now, the Mozilla Foundation added “emergency save” functionality for cases when Firefox crashes—next time you open the browser, you can restore the last session. This is exactly what we need in more applications.

This became another guerrilla post, but it should be clear that we benefit from applications to save continuously. So when there’s a web app that doesn’t have auto-save magic, let’s add it. And when there’s an important application that could use some of that magic too, let’s add it there as well.

About Me

I’m Jens (long: Jens Oliver Meiert), and I’m an engineering lead, guerrilla philosopher, and indie publisher. I’ve worked as a technical lead and engineering manager at various companies (e.g., Google); I’m an active web and tool developer (code optimization, digital defense), a contributor to web standards (like HTML, CSS, WCAG), and a book author (O’Reilly, Frontend Dogma).

I love trying things—in web development and engineering management, but also in politics and philosophy, where I hold to one idea in particular: that we can only be well if we take good care of everyone. Here on meiert.com I talk about some of my perspectives and experiences. (Interpret charitably but be critical—and share feedback and advice that makes my work better.)