I read
a great post this morning about the
Google Android Marketplace by Matt Hall, our buddy over at
Larva Labs. In short, Matt used a month’s worth of their sales data to illustrate how little market share Android has at this point and why he feels Google is somewhat to blame.
However, what caught my attention in this post was the conversation about why the iPhone has had such success versus Android-based handsets, even when adjusting for Android’s late-arrival to the game. I’ve had the opportunity to play around with one and my thoughts echo the comment from
Hamranhansenhansen on Matt’s post:
A good designer throws a ton of stuff away and saves engineers a million hours. For example, somebody at Apple chose a 480×320 3.5-inch screen and threw all the others away, and every developer on the iPhone platform, both inside and outside Apple, has been 100% focused on engineering for that screen…
Android, of course, is meant to scale to different screen sizes. And therein lies the issue. Designers are trained to focus on specificity, while engineers focus on scalability and ubiquity. At Google, that engineering mentality applies to their product design as well. Instead of building a great mobile device, Google is focused on building a great operating system that can be used by various mobile devices. Does any of this sound
familiar?
If Android is going to be successful, and therefore a viable platform for applications, Google needs to be aware of the pitfalls when designing for ubiquity.