By Harry McCracken | Thursday, January 28, 2010 at 5:43 pm
I swear I have no plans to dedicate this blog to links to John Gruber’s Daring Fireball, but he has another nice post up on the iPad and its implications. It’s worth reading whether you’re as giddy over the device as he is or are taking a wait-and-see approach–or even if you’re profoundly skeptical about the whole idea.
Gruber talks about the abstraction represented by the iPad–the way its interface shields the user from the minutia of the fact it’s a computing device in a way that no traditional computer does. He uses a car metaphor:
That’s where Apple is taking computing. A car with an automatic transmission still shifts gears; the driver just doesn’t need to know about it. A computer running iPhone OS still has a hierarchical file system; the user just never sees it.
Eventually, the vast majority [of computers] will be like the iPad in terms of the degree to which the underlying computer is abstracted away. Manual computers, like the Mac and Windows PCs, will slowly shift from the standard to the niche, something of interest only to experts and enthusiasts and developers.
If he’s right–and I think he is–the change is going to be less revolutionary than evolutionary. With computers, interface changes are nearly always about abstraction.
Want proof? Here’s John C. Dvorak–an odd bedfellow for Gruber if there ever was one–writing shortly after the Mac’s release in 1984, using a comparison he credits to Will Hearst II:
What the automatic transmission did for the automobile is what the Macintosh will do for personal computers.
Or simply consider the last thirty-five years of personal computing and communications:
It doesn’t matter whether you like abstraction or prefer to get your hands as dirty as possible. The trend is inevitable, and there’s no reason to think it’s anywhere near completion.
There’s no way that Windows or OS X can ever become utterly abstract, though. Both platforms have roots that stretch back to the 1980s, and which eliminate any possibility that you’ll forget you’re using a computer.
The cruft is especially thick on Windows, which still can leave you having to deal with the Registry and various security hassles and even the fact that an application may consist of thousands of files stored in multiple places on your hard drive. But it’s there in OS X, too. These operating systems have been abstracted about as far as they can be.
With the iPhone, and now the iPad, Apple took a step that’s necessary for further abstraction: It started over.
The iPhone OS’s technological underpinnings are based on OS X’s, but Apple threw a lot out. And when it came to the user interface, it didn’t rework the Mac look and feel–it built something utterly new. That approach couldn’t be any more different from Microsoft’s strategy with Windows Mobile, which retains as much as possible of Windows familiarity, from the Start Menu to dialog boxes to the freakin’ Registry.
By starting over, though, Apple gave up much. On both the technical and usability fronts, there are an array of things it’s either chosen to ignore or is working on but hasn’t yet incorporated into the OS. Obvious example: cut and paste, a mundane system function which didn’t make its way into the iPhone OS until two years after the first iPhone shipped–but which worked really well once it got there.
In its current state, the iPhone OS is still immature–and at times, abstract and limiting feel like the same thing. The OS still provides very little in the way of customization options, and still provides few ways for applications to get at data stored on the device. The inability to listen to a third-party music app while using a different program doesn’t feel abstract in the least; it’s a nagging reminder that you’re using an electronic device.
All of this is a more significant issue with the iPad than with the iPhone. The new device’s larger screen is going to make it a useful tool for applications which will never be key ones on the iPhone, and many of which are familiar from PCs and Macs. We began to see that yesterday morning, with Apple’s iWork office apps. All three are vastly more ambitious than similar programs for the iPhone will ever be, and reminiscent of programs we’ve used on desktop OSes for decades.
Their interfaces were the single thing at yesterday’s event that excited me the most. At the moment, though, they’re hobbled by basic limitations of the OS they run on. On the iPhone, for example, not being able to print directly is either a mild irritant or no irritant at all–but if you plan to use the iWork apps on the iPad, it’s could be a major pain in the neck.
Will the iPad be permanently crippled by limitations inherent in the current iPhone OS? Absent access to Apple’s software roadmap, it’s impossible to know for sure, and the company isn’t telling. I do have some guesses, though:
Apple, of course, isn’t the only company driving further abstraction of the computing experience. With Chrome OS, for instance, Google is pretty much trying to abstract everything out of the operating system except for the Web browser. (Apple limits you to the apps it chooses to offer through the iTunes Store; Google doesn’t let you run apps, period.)
I have no plans to eliminate traditional computers running traditional OSes from my computing regimen any time soon, but I’m glad both companies are scaring themselves–or at least some of us–with radical change. Which is why I think the iPad is a significant product even if version 1.0 is missing any number of bells and whistles which I’m not willing to live without just yet.