Command-S has to go!
Have you ever kept track of how often you hit Command-S on an average day? However you use your Mac, whatever kind of apps you are using: chances are that hitting that comforting key combination every few minutes has become a subconscious habit for you. For me, it's so bad, I sometimes hit Command-S while filling out a web form, wondering where the heck that Save As dialog box came from. The question is: Why? Why do we do this? Why isn't there a better way? Oh, wait, there is!
If you have an iPhone at hand, try this: open Notes, create a new note, and then hold down the power key to switch off the iPhone. Re-launch the phone, and you're exactly where you left off, although, courtesy of the Notes app, you did not have to explicitly save anything. No explicit saving, no worries.
Try the same thing on a Mac, and you should better make sure to hit all the right buttons when asked if you want to save or discard unsaved changes for all your open documents. And if you have any as-yet-unsaved documents, take a moment to give them names and decide where to save them.
Admittedly, the iPhone has one major advantage when it comes to document management: its default user interface does not have an equivalent to the Mac's Finder, so that any documents are only accessed directly from within their parent applications: email attachments are only viewed within Mail, notes are only handled within Notes, etc. Still, there are some applications on the Macintosh that do behave in a similarly user-friendly way, e.g., Stickies: there is no need to save newly created notes. In fact, that little application does not even have a "Save" command.
I just wish that the way we save documents would be changed system-wide, so I wouldn't ever have to bother with manually saving a document ever again.
Save that for me, Mac, will you!
Some of Apple's own iLife applications use a method that might be useful as a starting point: when creating a new project in GarageBand, the first thing that pops up is the "Save As..." dialog, in which you name that project and decide where to store it. And that is exactly what, in my humble opinion, every application that works with documents should do: instead of saving a document before closing its window, it should be saved right after it is created, i.e., well before you invested any time and effort in that document's contents!
After that, the software would save any open documents automatically: regularly while you're working on them, and every time you close a doc window. In other words, once you've created and named a document, you should never have to hit Command-S for that document again. Ever.
Unless you wanted to explicitly create a snapshot, or version, of that file, similar to the date-stamped backups in Time Machine, so you could switch between these different versions. Instead of answering the question of whether you'd like to save or discard changes every time a document is closed (unless your left hand had just previously happened to instinctively hit Command-S for the umpteenth time), you'd just revert back to a previous version when you actually want to. Which, I'm quite sure, happens a lot less often than having to answer that "Save this stuff, dear user?" prompt when closing of a document window...
Imagine what this would mean: no more data loss because you failed to hit Command-S in time before the power outage swept through your area; no more confirmation that, yes, you do want to save the changes to disk every single time you closing an app; no more RSI because you sub-consciously hit Command-S ten times for every five words you write.
A habit overhaul is due
Having to manually save documents is one of those computing habits that -- like quitting applications, and quite a few others -- we have gotten so used to that we don't question their usefulness anymore. And although a much more user friendly approach is technically feasible, we still stick with what we know, even though we don't know just why. It's time to change some of those habits, and why not start with how we tell our computers how to save documents?
Do you see other "habits" imposed on us by our computers that need a serious overhaul? Please join our discussion and let's talk 'em through!
Categories
MacComments (8)
Read More Entries by Jochen Wolters.

Exactly the way the Newton worked, as well...bring back "soups" in the iPhone and we're back to the future!
I always turn off auto save in my apps. I often rely on the "revert to saved" option when I 'm trying out a new design and decide I don't like where it's going.
Those are great comments. Thanks!
I can see how you would want to open a new document to quickly capture an idea or thought that you do not want to store in a file, so asking for the file's name and location right after creating the document may not be so great, after all. Kay's idea to have the application temporarily store the file (without explicit user interaction) and ask for it to be saved when the window is closed does make a lot of sense in this scenario.
Devising a strategy about when and what to write to disk based on the amount of changes implemented by the user, how much time passed since the last save, etc. largely depends on just how much time it takes to store a document, i.e., how much interruption this would cause for an app's user. I can't see a standard answer here, but I still wish that developers would at least try to come up with _something_ that does away with the Command-S "madness". ;)
Interestingly, none of you have criticized auto-saving of files per se, "just" the timing of the (modal) dialog to write out a document onto a hard drive for the first time. Hence: if you could freely decide on how this feature should be implemented in a future OS release, what kind of approach would _you_ choose?
The iPhone also uses Flash memory as it's only memory - there is not the same need for a separate "persist my data" operation.
There may be file system issues that need to be cleared up, first.
When we finally get "Sun's" ZFS file system as bootable OS files, it can make revision updates periodically, which don't overwrite your existing files. That way you can revert to an earlier version, seemlessly.
Some of Apple's software does automatically save backups.Then Time Machine can save them on hourly intervals. But, Apple's HFS+ journaling file system doesn't seem ready to make it as fully automatic as you seem to want. But one day? Sure. Apple seems to moving in that direction.
I also disagree as I DO create documents that I have no intention of saving--and I don't.
This is exactly the way Apple's Lisa worked.
I disagree somewhat, not that I wouldn't want my data to be safe, but presenting me with a "Save as..." dialog every time I create a new document is lame and against good interface design:
When I create a new document, my intention is to create new data. I think about "I need to write this down" when I open a Sticky, for instance, I do not want to bother about thinking where to save it, because it disrupts my work. Incidentally, Sticky.app doesn't ask me ;)
I much rather have the application auto-save my work somewhere safe and when I close the document without explicitely saving it, it should then discard the temporary file, after asking me what to do, of course.
For certain types of applications saving takes a considerable amount of time, necessating an incremental approach to saving, if it is done often (via auto-save).
It can be done with the existing means, but it's not an easy thing to pull off, performancewise.