Home
BYTE Newsletter
Keep up with all the BYTE News and Reviews

Subscribe
Thomas Claburn

Thomas Claburn

Editor-at-Large

Android, Chrome OS Marriage Denied

Comments | Thomas Claburn, InformationWeek | March 22, 2013 08:52 AM


Google Chromebook Pixel: Visual Tour
Google Chromebook Pixel: Visual Tour
(click image for larger view and for slideshow)
Google's decision to put Android and Chrome OS under one manager does not mean the two operating systems will be married.

Android and Chrome OS, will "remain separate for a very, very long time," although they will overlap more than they do presently, said Google executive chairman Eric Schmidt at the company's Google Big Tent Activate Summit 2013 in New Delhi, India, on Wednesday.

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

However, Schmidt's assurance might not be the last word on the subject, given past statements about operating system unification.

A week ago, Google CEO Larry Page announced that Andy Rubin has decided to relinquish his oversight of Android to pursue other opportunities at the company and that Sundar Pichai, senior VP of Chrome and Apps, will assume responsibility for Android.

[ It's not wise to get too attached to some Google products. Read Google Keep Arrives, But For How Long? ]

The executive shuffle revived longstanding speculation about whether Google will unify Android and Chrome OS into a single product.

The possibility of a merger has been discussed at least since late 2009 when Google first made Chrome OS code available to developers. No less than Google co-founder Sergey Brin said at the time, "Android and Chrome will likely converge over time."

Since then, others with some knowledge of the technology at issue have continued to believe that unification of the two operating systems was inevitable. For example, Paul Buchheit, who helped create Gmail before leaving Google, opined in late 2010 that Chrome OS would either perish or be folded into Android.

Although Buchheit's obituary for Chrome OS proved premature, his reasoning, explained in greater length in a blog post, bears further examination. He said that Android would gain the benefits of Chrome OS, such as security and the ability to start rapidly, the implication being that convergence will make Chrome OS redundant.

In other words, Chrome OS is doomed because it offers a subset of what Android offers.

"Once Android has all the benefits of ChromeOS, the most obvious difference will be that ChromeOS lacks the thousands of native apps which are popular on Android," he wrote. "Android apps are closer to Web apps than Windows apps in terms of security and manageability, so eliminating them doesn't seem like much of an advantage for ChromeOS."

But Google won't eliminate Android apps or drop Chrome OS. It will add an Android app compatibility layer to Chrome OS. Buchheit observed then that the obvious difference between Chrome OS and Android is that Chrome relied on mouse or trackpad interaction and Android relied on touchscreen interaction. That distinction has disappeared. Chrome OS now supports touchscreen interaction, as can be seen in Google's recently introduced Chromebook Pixel. Chrome OS and Android are already closer together than they once were.

The question is whether that convergence will continue and how far it will go. Much of the speculation on the topic assumes that Chrome OS will be thrown under the bus because it's so much less popular than Android. But Chrome OS would be a lot more popular if it could run Android apps.

If you want a picture of Google's future, look at BlueStacks, a company that offers a way to run Android apps on a Mac or PC. By implementing something similar -- probably using its Native Client technology -- Google could provide Chrome OS users with access to the Android app ecosystem while retaining the security benefits and cloud favoritism of its browser-based operating system.

That's why Sundar Pichai, the man in charge of Chrome OS, is now overseeing Android.



Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

COMMENTS

Tune In to BYTE
Facebook Twitter LinkedIn Newsletter RSS
Whitepapers
whitepaper
In this paper you will learn the five trends shaping the future of enterprise mobility. Learn how the rise of social media as a business application, the lurring between work and home, the emergence of new mobile devices, the demand for tech savvy employees and changing expectations of corporate IT will fundamentally change the workplace.
whitepaper
In a survey of more than 1,700 information workers (iWorkers) in North America, notebooks, desktops, and smartphones were found to be “must-have” devices, while tablets, slates, and netbooks were relegated to “nice-to-have” status, according to a commissioned study conducted by Forrester Consulting on behalf of Dell and Intel.
Sponsored by: Dell
Upcoming Events