ro

Google officially announced the Nexus One today, and it seems pretty cool.  I haven’t had a chance to play with one yet, but by most accounts, it’s worth checking out.  I believe it will be a successful device, along with the Motorola Droid and the HTC Droid Eris.  However, there seems to be a lot of sentiment that this is playing out like the PC vs Mac wars a decade or so ago, and that slowly app developers (and in-turn users) will all gravitate towards the more open Android platform.  The argument is that Microsoft excelled because it was hardware agnostic and did not control the ecosystem (thus allowing it to innovate), whereas Macs struggled because they controlled the entire experience (here’s a good take on this).  In the mobile marketplace, the argument continues, Android will eventually win out because it’s completely open.  Never mind the over simplicity (i.e. Jobs left, the hardware started to suck, etc.), there are some good parallels to make the analogy fit.

I, however, completely disagree.  This market is much, much more nuanced.  The reason is that there are two major differences between different phones that affect user behavior – input mechanism and screen size.  For example, here’s a list of the different screen resolutions for Android devices:

800 x 480
600 x 800
320 x 480
240 x 320
854 x 480
240 x 400
1024 x 600

And Android is only now becoming popular.  Some Android devices have keyboards, some are touch only, some have pointers, some have extra buttons, and some have sensors others don’t.  With the computer, everyone had a similar keyboard and mouse.  Users had different size monitors, but the big difference was that you could get away with cropping and not using the entire monitor for computer apps.  On a phone, where the screen is already so small, not using the entire space is much more significant.

This is the same issue that plagues Blackberry right now (well, that and terrible API implementation/documentation).  Whether it’s the Curve, Bold, Pearl, and so on, every device has a different resolution, and so apps need to be tailored appropriately.  I’m not the first to realize this is an issue (official Android documentation and another post).  The iPhone, on the other hand, has one screen resolution 320 x 480, and one input mechanism, touchscreen.

That all said, I believe that Android will thrive, but it won’t be the same way as Mac vs PC.  Bill Gurley’s piece (a must-read, in my opinion) begins to get at the nuanced differences, but Android is still a smartphone platform, which puts it head-to-head with the iPhone.   It is very lucrative for manufacturers and carriers to use Android instead of paying a licensing fee (they actually receive ad revenue share for using Android).  But for consumers and users of apps on both devices?  I still think the iPhone will be a better experience.

Two additional interesting factors to consider – if feature phones (i.e. non-smartphones) begin to adopt Android in full-scale, and the continued success of the iPod Touch and iTunes store (remember, you can’t use your iTunes music on a non-Apple device).

Last night, I was driving home from my sister’s place in the east bay, and after checking Google Maps and seeing all green roads (i.e. no traffic), I decided to take 880/Bay Bridge to get back to SF.  Little did I know it was green because there was no traffic on the bridge (due to the closure).  Had I known beforehand, I would have saved a full hour.  In a moment of tragic comedy (okay, it was not that bad, but good thing I had company), Caltrans decided to alert me after I passed the traffic-filled toll plaza on the San Mateo Bridge that the “Bay Bridge is closed, seek alt route.”  Thanks.

I’m not alone when I say I’m often running late to lunches and social gatherings.  Or oftentimes I get delayed when I need to travel out of the office for a meeting.  The one thing that’s constant in all these situations – my phone.  My mobile device always knows where I am.  My calendar always knows where I should be.  Why can’t these two merge?

Now, I know this is difficult on the iPhone since there are no background apps, making it difficult to keep updating location (though some folks have found workarounds) .  But on Android, this should be relatively easy.  With the proliferation of LBS, my phone knows where I am at all times.  It could tell, for example, that if it’s 8:45 AM and I am more than 15 miles away (or there’s traffic) from my 9 AM calendar appointment location, that I will be late.  It could then send a text/email to the other attendees (or at least the organizer).  Little late to dinner?  Perhaps an integration to OpenTable.  Flight late, meaning I can work later?  An integration to TripIt would be help.  Yes, many folks have admins to help with this, but it really should be automated.  Last night, my phone clearly could have known I was heading home to SF via the Bay Bridge, and alerted me of the closure (the news was all over Twitter, which I unfortunately did not check before leaving).

None of this is ground-breaking, or extremely tough to do.  Google is probably best positioned to do this, but perhaps there’s a startup already hard at work (I hope so).  I’m looking forward to the day when all these services are combined and I can comfortably know I’m being alerted.  In the meantime, good luck to Caltrans on the repairs, and all commuters who usually take the Bay Bridge daily.