Linked by Thom Holwerda on Mon 14th Apr 2014 16:40 UTC

From a 2006 (pre-iPhone) Android specification document:

Touchscreens will not be supported: the Product was designed with the presence of discrete physical buttons as an assumption.

However, there is nothing fundamental in the Product's architecture that prevents the support of touchscreens in the future.

The same document, but a few versions later, from 2007 (post-iPhone):

A touchscreen for finger-based navigation - including multi-touch capabilites - is required.

The impact of the iPhone on Android in two documents. Google knew the iPhone would change the market, while Microsoft, Nokia, and BlackBerry did not. That's why Android is now the most popular smartphone platform, while the mentioned three are essentially irrelevant.

Permalink for comment 587061
To read all comments associated with this story, please click here.
Member since:

You are clearly not a software developer and you're giving Apple way too much credit.

You are clearly not an interaction designer.

Yeah, you can "hack out" something in a day or two. But so often, the devil is in the details.

Apple would have spent months fine-tuning interaction speeds, thresholds, algorithms for handling the multi-touch inputs. All of this stuff seems invisible once the product is launched to anyone who wasn't involved - "just works" is damn hard, and too often people that don't understand the work involved in perfecting these interfaces and their interactions massively underestimate just how difficult and time-consuming this part is.

Reply Parent Score: 4