Header Ziff Davis Enterprise
Advertisement
Advertisement
Thursday, May 26, 2011 12:01 AM/EST

Google Chrome OS Smartphone Coming, Pundit Says

How do you feel about a smartphone based on Google's Chrome operating system, the Web-based OS currently making its way to Amazon.com and Best Buy online via Samsung and Acer notebooks June 15? New chrome logo.png

I can imagine the marketing campaigns for this. Chrome Home with Chrome Phone!

On the Street.com, Anton Wahlman, a former sell-side equity research analyst covering the communications space, opined that Google will launch its own Google Phone and that it will be based on Chrome OS, not Android.

Step into my Hot Tub Time Machine for a moment. Recall that in January 2010, Google rolled out the HTC-built Nexus One smartphone unlocked and with a T-Mobile contract, selling it solely online.

It surely tested the waters, but then promptly sunk to the level of developer phone.

What Wahlman is proposing is different. He sees Google taking the Chrome OS cloud paradigm -- the verified boot process and speedy startup -- to the phone form factor.

The reason? Security perks of the cloud. While current Android devices accept application downloads, Wahlman argues that a cloud-centric OS such as Chrome with apps solely in the cloud. He noted:

This device would only have two major software parts -- the OS and the only allowed browser. However, the OS treats the browser as a de-facto hostile application, not allowing it to modify the OS including locally install any applications.

Like the notebooks Chrome OS currently powers, the Chrome OS phone would require less memory, less local storage and a less powerful CPU.

Theoretically, Google could launch these "shells," which could be easily replaceable because users' data lives in the cloud.

This model would bury Research In Motion's BlackBerry Enterprise Server, noted Wahlman, with Chrome OS providing a simpler management console for provisioning device access, activity in the browser and account device management.

Interesting theories. Google had promised that Chrome OS was intended for clamshell-style computers only and yet we know Google engineers are toying with Chrome OS tablets. Why not a phone?

I'm thinking Google could maybe sell these bad boys for $99 or less, subsidized by ads. That would be a good price point for those tired of spending $200 or more for fully Web-enabled phones. But would it be good enough for carriers who like the phone margins?

Wahlman believes Google could use pure VOIP via Google Voice and Google Talk. Hmmm. The last time Google tried to disrupt the carrier market in such stellar fashion, only T-Mobile played ball; the market leaders coughed and laughed.

Then again, if Google launches its own mobile broadband network, an offshoot of Google Fiber, maybe Google wouldn't have to curry favor with the carrier giants. Just sayin'.

Wahlman has four pages, which you may read here, to fortify his argument. I can buy it, but only in so far as Chrome OS sees a modicum of success in its current instantiations.

I'd like to hear your thoughts on why this would or wouldn't work.

TrackBack

TrackBack

http://googlewatch.eweek.com/cgi-bin/mte/mt-tb.cgi/22961

Comments (2)

Cloudbuster :

Talk about having your "head in the clouds".

* Google already kicked dirt on buying spectrum to setup a credible wireless presence (3G/4G/LTE). So to have reasonable reach you'll have to use bandwidth from the carriers and that isn't going to be cheap for a "full cloud" device.
* Google setting up WiFi everywhere is a pipe dream, they'll hit some major centers and ignore the rest of the country. Google WiFi available while I'm booting down I-95 through the middle of nowhere in upper FL? Nope, no service, sorry. Fail.
* Lots of spots where I want to use my phone that have lousy coverage (terrible data rates or voice only in some spots). With Android I can still lookup names, make voice calls, run apps (like my expense app), etc., etc., etc. On a "Chrome" phone? Nope, sorry. Fail.
* A BES killer? Central management for Chrome? You might be able to manage the device (what's to manage on the device, there's nothing on it), but now you've got to manage these individual apps, permissions, data, etc. Think that all these "cloud apps" are goig to have a single "GUI" to administer them consistently, have uniform access controls to the data? Everyone providing a "cloud app" trustworthy? How long before the first "Sony" crops up and leaks all of your "cloud" data when your security creds get exposed. Fail.


Puru :

I see it as a long term bet/hedge by Google than a near term strategy. Few things need to be resolved for this to work:
- Internally, a clearer alignment between Android and ChromeOS roadmaps.
- Ubiquity of bandwidth, even if for target metropolitan markets. We know how flaky this can be. The current HTML5 model does not guarantee a dependable, meaningful offline behavior using data that is cached by an application, not user.
- Cost of bandwidth, or at least some predictability to how much you will pay when your device is basically useless without the cloud. Specially with the disappearance of unlimited data plans in US, this is definitely a concern.

Post a Comment

 
 

Advertisement

Advertisement