When I am using OS X, I work in two ways.
One way is enviromentally-oriented. For example, I open Chrome to look at websites. I launch an environment to access a bunch of things of the same type; in this case, websites.
Another way is project-oriented. I almost never open InDesign by itself. Instead, I launch a project; in this case, a specific design that I’m working on. I just click on the file I want, and the relevant application opens it.
Of course, it’s not just work. The same goes for play and (gasp!) consumption too. I open iTunes to open an environment for music. But I click on an mp4 file to launch VLC to play a video.
I like having these two modes of workflow available. To me, it makes no sense to open InDesign, and then click on “File”, and then click on “Open”, and then browse through the file architecture to find the project I’m working on, and then finally opening it. Even with a keyboard shortcut, accessing the file architecture from within the environment feels like an unnecessary chore. Similarly, I cannot even imagine clicking on a specific URL (file?) to open Chrome. Sometimes it just makes sense to launch environments, and other times it just makes sense to launch projects.
In fact, the two workflow modes are not merely two ways to work (and play and consume). They represent two ways of thinking: tool-oriented and task-oriented. Of course, in thinking about what to do, one always has to think about both how to best do it and what needs to be done. But the questions can be prioritized. Sometimes it is more important to think first about the tool to use, and other times it is more important to think first about the task to be accomplished.
The problem with the iOS environment is that it exclusively privileges the environmentally-oriented workflow. While, to emphasize again, there is nothing wrong with thinking about tools first in some cases, it’s entirely unobvious that this way of thinking is preferable in all cases. Yet, the universal preference for tool-oriented thinking is exactly what the core design philosophy of iOS assumes, builds on, and mandates. Everything is to be done from an app environment. And so I am worried that the same core design philosophy appears to be creeping into OS X with the increasing prominence of iCloud in Mountain Lion.
Now, e-mail, there’s always been a better way to find stuff. You don’t keep your e-mail on your file system, right? The app manages it. And that was the breakthrough, as an example, in iTunes. You don’t keep your music in the file system, that would be crazy. You keep it in this app that knows about music and knows how to find things in lots of different ways. Same with photos: we’ve got an app that knows all about photos. And these apps manage their own file storage.
And eventually, the file system management is just gonna be an app for pros and consumers aren’t gonna need to use it.
Jobs is clearly right, about email and music and photos. What is doubtful is that his point generalizes: that the environment-oriented workflow is always the better way of managing things.
Importantly, contrary to what Jobs seems to think, the project-oriented workflow is not exclusive to geeks and pros. Recent discussions on the shortcomings of iCloud makes this point apparent (my emphasis):
But Pierce added that “the biggest limitation to Dropbox is that it works with traditional file and folders.” There are times such a traditional approach feels entirely appropriate—as with text editors, where users are accustomed to saving individual documents.
Even ordinary users, when it comes to writing, prefers to launch a project, and not to launch an environment. It’s not, I believe, merely a matter of tradition versus the future. Instead, the two modes of workflow exist because there exist two ways of thinking, each good in some contexts but not others. (Of course, what those respective contexts are may well vary from person to person.)
Feel free to talk to me on Twitter: @RagingTBolt.