Is it really possible this is already a valid question to ask ? Can this really be true?
“Desktop First Mobile Second” slogan is the most irritating marketing (truth economy) slogan for today. Among few other of Google executives “revelations”, revealed in numerous interviews appearing today … Carefully prepared well in advance, I assume.
That slogan is of course not true. It is a part of a grand schema devised to replace Android. As any other legacy software, Android has to be “decommissioned” and current flora and fauna in that jungle has to be carefully migrated to Chrome OS. We all know that, Google knows that and, I hope, this is not debatable.
I think I know a thing or two about system software, hardware and a such, after two + dozens of years in IT. I also think it is very safe to assume that Google engineers are more than capable of grafting anything they want on top of Linux kernel. Using almost any of the devices they have also designed. Therefore.
Where is Mobile Chrome OS?
It is very likely it is already running in the lab, on Nexus hardware. From Nexus 4 to Nexus 10.
You my dear reader, are not a very naive person, are you not? As a such you know that engineers are the last group of people deciding what and when is going to be actually transformed into the product and released. So, I am talking to you here: The thinking reader.
My prediction is that Chrome OS on mobile devices will be released VERY VERY CAREFULLY. With lot of supposedly technological excuses for executing this very slow and touchy approach. I might be so bold to predict a detail too: Google will play the good old “new OS needs new CPU” stunt. So, Google keynotes will start claiming this:
ARM64 + ChromeOS = next mobile ecosystem evolutionary step (aka MobileChrome or whatever)
Why? Simple explanation: delaying tactics. ARM64 will be presented as “necessary” to run Mobile Chrome OS. That will give Google enough time for safe transition from Android (gasp!) to Mobile Chrome. And of course for milking the Andro-Cash cow. Which activity never hurt anybody, especially not the legions of euphoric share-holders.
Therefore. Google sure does need it, and wants to keep it, all VERY “evolutionary”. In the past, Android “revolutionary” ecosystem was unleashed too soon from Google kindergarten project. By good engineers, but alas too inexperienced in everything else. Like money is, for example.
These days fragmented Android ecosystems reminds me of one enormous un-maneuverable (fragmented) ship. That has to be somehow, carefully retired back to final port. Not demolished and sunk in the middle of the sea, altogether with valuable cargo.
And on this huge Andro-Ship there is one “under the deck” habitat, inhabited by few hundred millions of faithfuls who must not be disappointed.
3 thoughts on “Chrome Mobile OS. Not if and not when, but how.”
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.
@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.
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.