Our pals at JK on the Run put up an excellent piece today breaking down Google's supposed (or blatant, depending on who you ask) favoritism regarding the latest OS versions, features, etc. Basically it boils down to this: Has Google put some of the latest features (i.e. Buzz, Google Maps Navigation) on the most current hardware with the newest builds? Absolutely. And why wouldn't you show off your best software on the best hardware? Writes Kevin C. Tofel:
I ask myself: if I were Google and I wanted to rock out a new app and build the biggest buzz, I’d get it on the heartiest hardware first so it really shines from a performance perspective. I’d also pair it with hardware designed to show it off — the Droid car dock morphs what’s essentially a software product into a look-alike, standalone GPS device.
And as for your older Android phone not yet rocking Version 2.0 or 2.1, remember that unless it's the Nexus One (or the G1, we suppose), updating devices such as the Motorola Cliq -- or the Cliq XT ... or the Devour -- is going to some doing, as Motoroblur is only on Android 1.6 at current. And that's not Google's fault.
Who chose to put Android 1.6 on this new Android device? It certainly wasn’t Google. If you have to “blame” someone, choose either Motorola who made the phone or Verizon who decided to sell the phone. All Google does for this phone is provide versions of it’s mobile platform to the phone maker.
Those are all points we've argued before, and we bet we'll be arguing them for some time to come. Is the platform fractured? Yep. But that's not Google's fault, just as it wasn't Microsoft's fault when Windows Mobile (RIP) saw itself running in various versions on a number of devices. [JK on the Run]