ChromeOS is for applications where serious user input is required via a keyboard. In other words, it is a data input or data editing device as well, rather than just purely a data consumption device. Typical examples where this approach would be successful are public access terminals (eg. in libraries) where grubby fingers making screens dirty are not wanted, personal devices for school/university students to access information as well as type in their coursework/thesis, information/service/POS terminals and also office terminals in organisations where you are using the OS to access server based applications. In this form ChromeOS can be regarded as a next generation thin client with universal go anywhere connectivity. ChromeOS (or Android on tablets for that matter) can also replace the traditional physical sit-on-your-desk Windows desktop PCs with a go anywhere universal access device. I can see businesses getting rid of desktop PCs and replacing them with ChromeOS accessing virtual Windows desktops running on virtual servers via RDP. Office workers would then use a ChromeOS netbook or Android Tablet as their only interface device (and a take with them personal device).

We have already seen this trend with laptops overtaking desktop PC sales, and netbooks eating into laptop sales. ChromeOS as a universal access terminal is a natural progression of this trend to mobility, and I believe it along with mobile and embedded devices like mobile phones and TVs is the future of personal computing. When in the office workers would run Windows desktop applications from their ChromeOS/Android device through remote access via WLAN allowing the saving of power and desktop clutter, not being ties to one seat in one office, and being able to access the same Windows desktop applications and data from anywhere including on the move via 4G mobile networks or WiFi.

I think ChromeOS will become a superset of Android – in other words you will be able to run Android applications within Chrome OS, although some thought will need to be given to how the Android interface will operate within ChromeOS.

There are some uses for which the traditional desktop PC will remain eg. technical users requiring powerful graphics cards and very high definition screens – eg. CAD technicians and graphics artists, but I think in the future that traditional desktop PCs will increasingly become a rarity.

Keeping all that in mind, if the real argument is that the x86 port of android needs more support or that x86 does not have much of a future in the mobile space… those are perfectly reasonable arguments.

The strategy of Apple is different to that of Google. Apple like control & simplicity – Google prefer open & variation.

There’s a lot for Google & the community at large to gain from the approach. They’ve not put all their eggs into one mobile basket – both teams can learn & understand what works, what users want while gathering intel (metrics).

Apple’s current approach is successful for them but I doubt the long-term viability of keeping everything in-house.

Ironically, I remember a similar skeptical and disappointed article by Om when he realized that Android is not a single ‘Google Phone’ like the iPhone, but a platform. Wish I had time enough to search for that article and post a link here now…

Chrome and Chrome OS will have Native Client (NaCl) built-in for native code, from day one.

So, Android could be used in a same way by Google inside Chrome OS….

Scenario #1

Sergey takes dog behind barn (Larry sobbing in foreground).

BLAM!

Scenario #2

Sergey takes dog behind barn (Larry sobbing in foreground).

BLAM!

yelp yelp yelp!

(shotgun jams)

-expletive-

BLAM!

YELP YELP YELP!

BLAM! BLAM! BLAM! BLAM!

“Finally!!”