My goal with this blog

I write about relevant changes in the way that people use the web and how startups are built to provide services and products for this ever changing wonderful thing we still know as "the web." As a former entrepreneur turned early-stage investor, my greatest hope is for this to be useful to other folks that are like me in the hopes that they can avoid some of the mistakes I've made.

Making it a software problem: why the iPhone's keyboard rocks

Lots of people have been spending way too much time blogging about the iPhone (though believe it or not, I still think it is under-hyped), so I'm going to stay away from reviewing mine. That said, I did want to make a quick software comment that the iPhone's keyboard makes clear as day.


Whenever you can turn a piece of complex UI from hardware to software, you seriously accelerate the rate of improvement of the general interface.

I've had two other Smartphones, the Treo 700p and the Nokia e61i. Both have the full tactile keyboard that the RIM Blackberry pioneered— which despite looking like it was made for Smurfs, works remarkably well. However, you make two key compromises with it: the loss of real estate that could either go to the screen or to a smaller overall device, and a hard upper limit as to how fast you will be able to go. In the case of the iPhone, it seemed to me that Apple's engineers valued screen over buttons and went with the soft keyboard as a compromise.

And despite the overwhelmingly positive reviews of the soft keyboard, I never in a million years expected that I would actually find myself typing faster on the virtual iPhone keyboard than on a tactile one. Yet three weeks into it, that is exactly what has happened— I can now type faster on the iPhone than I ever did on the Treo or the Nokia, thanks exclusively to the interface and to the simplistic spelling correction algorithm. More importantly, the rev cycle just went from 12-18 months (the average amount of time between my hardware updates) to whatever the frequency of the iPhone software updates shakes out to be. They've taken something that was tied to the limitations of the physical world and moved it squarely into the realm of the virtual.

ReadWrite web had a thought provoking post on exactly this topic, "digital physics," arguing that an interface which borrows just enough from real world physics but takes it beyond those constraints is the future of all user experiences. At the time I saw it as an esoteric point, but now that I've experienced it, I'm completely sold.

And of course there are other benefits to moving the interface into software. When Tivos replaced VCRs we got a big boost in "recording productivity" just because of how much more heavy lifting was being done in code. I suspect we'll see a lot of the same types of things in the iPhone's virtual keyboard, especially as the API is opened up to third-party developers.

That said, there are clearly examples of when moving an interface from hardware (buttons and knobs) to software can really screw things up: BMW's iDrive and all of those fancy universal remotes being good case studies. It would seem to me though that most of these counterpoints are better examples of poor implementations and not so much a weakness in the idea of moving hardware interfaces to software.

One final caveat: there is this famous Alan Kay quote about how people who are serious about software ultimately build their own hardware (which incidentally Jobs keeps using about all things Apple). I've never understood it until now. It is after all the incredible sensitivity of the panel in the iPhone that lets the software do its magic, and we'd do well to remember that bit of wisdom before even considering the approach.