Chrome Mobile OS. Not if and not when, but how.

Chrome Mobile OS?

The Android Emulator home screen. (Photo credit: Wikipedia)
The Android Emulator home screen. (Photo credit: Wikipedia)

Update 2017 Oct 16

Ah was I right again?

Update 2015 Oct 30

AndroChrom

(AFAIK, name invented by me today 🙂 )

Alphabet’s Google to Fold Chrome Operating System Into Android (The Wall Street Journal)

  1. Which one is “folding” into which one?  None. They are merging into one.
    1. Technically Chrome OS is a real OS
      1. My (safe) speculation is that as much as possible of the Chrome will be kept and used as foundation.
    2. Android is a kindergarten OS, that was released to early and was never meant to be.
      1. But children liked it.
    3. But even now it is very likely Chrome Books will be gradually updated (as ever) to the state of being totally “new” OS. Which is not that “new”.
      1. Which for Chrome Books is just new part of the top layer, to host JVM
        1. And “something more” so that Android App’s can run natively
        2. This in essence is not far from new (Android) SDK rewritten to run on Chrome OS
        1. With Chrome Browser untouched of course.
  2. Marketing is all about Manipulating the Focus.
    1. All the news that you will initially read on this subject is about manipulating your focus away from the point 1.
  3. Name is extremely important. My speculations bellow have ignored this point.
    1. Of course it will be based on the word “Android”, as per point 2
      1. Certainly “ChromA” is out of the question
      2. Like “ChromUX” was out of the question
        1. Regardless of the fact that Chrome OS is Linux + Chrome browser
  4. 2017?
    1. As I said bellow: transition will be done extremely carefully
    2. By 2017 Google will know and see where is the best place to attack Microsoft
      1. Win10 situation will be definitely clarified by then

So here we are. Yer another speculation turned out not to be a speculaltion.

Update 2014 Sep 12

Well almost exactly a year latter this little (nasty) speculation of mine, it seems, might not be that speculative?

http://www.theverge.com/2014/9/11/6135273/chrome-os-begins-running-android-apps-vine-evernote-duolingo

One (extremely) careful migration from Android to Chrome OS has started. Just after Android Lemmings have readily swallowed one very large does of anesthetic called: Android L.

But today (I noticed that) a lot of people are scrambling back to to this Google video from June 2014.
Google I/O 2014 Keynote.Watch very carefully:

Sep 08 2013

Well of course I could not miss the whole of today’s Google “Chrome Apps” charade. How could anyone ? There was also one single thought I could not escape. One agonizing question drilling into my consciousness (hint: I am being overly sarcastic here) One sinful question I have to confess :

What is the Android Staying power ?

Next page please.

3 Replies to “Chrome Mobile OS. Not if and not when, but how.”

  1. Google should speed up the process for switching to ChromeOS for Nexus. I use ChromeOS exclusively at home and for travel. I think it is a fairly secure platform. I don’t feel the same on the Android phone I have. I don’t use the Android phone to access any personal finance sites, or even work related stuff. Even when I am on the road, I’d rather tether the Chromebook to my Android phone and access my bank that way, than use the bank app on the Android. I just think ChromeOS is much more secure ecosystem. I use the Android phone more as a Google Maps enabled GPS and to make calls, which I am sure ChromeOS can do as nicely.

  2. @Saqib thanks for your comment. I do agree that Chrome OS “feels” more secure, quick etc … And it certainly should be. Apparently “ChromePhone” is comming and it seems pretty certain Google is going to *replace* Android with ChromeOS. Not merge but replace.

  3. If google releases chrome OS mobile, it will finally be able to compete with iOS. I’ve been researching as to why iOS is much more fluid and always seem to have a better battery life and better apps compared to android is it is because of the language and kernal differences. iOS uses assembly language that speak directly to the phone while android uses java that speaks to a virtual machine that then speaks to the phone thus causing the (impossible to fix) lag. That’s why iOS requires less ram and a smaller battery. luckily for us chrome OS is build under a similar language and kernal that iOS is and is already getting fantastic battery life on the chrome pixel 2 and the speed is insane. The webbrowsing speed even beats out a macbook pro 2015 retina display! the only bad thing is hopefully we can install it into my nexus devices.

Leave a Reply