A long time ago, in 2016, the internet learned about a supposed Google initiative to merge Chrome OS and Android. It was to have the codename Andromeda and would unify all of Google's computing platforms so that they all used the same operating system. It made sense in many ways; it is similar to what Microsoft is doing with mobile, tablet and desktop software and supposedly the direction Apple is moving with iOS and macOS. Codenames and rumors aside, what ended up happening was the ability to visit the Google Play Store with a Chromebook and run Android apps natively.
This was a big deal, and if it was what Andromeda turned out to be it was certainly enough. Everyone benefits from having Android apps available on Chromebooks — Google can sell more and we can use them better because there will be an "app for that" whenever we need one. But the idea of Android and Chrome merging never really went away. It just got a new codename: Fuchsia.
Fuchsia got its name, according to some of the developers, from existing projects.
Project Pink was an original idea from Apple's engineering team when they decided it was time to build a new object-oriented operating system with a new user interface, and the notes were written on pink index cards. Project Purple was the original name given to prototype production of a touchscreen phone from Apple; the iPhone. The original developers of Fuchsia are well-versed with this history, as they were also part of former projects like BeOS, iOS, and WebOS.
But an operating system needs more than a name. And without Google telling us anything about its new project, we're left to piece together all the breadcrumbs the internet can find. Here is what we know so far.
Fuchsia is not going to replace Android or Chrome OS
Android is a complicated thing. It can be thought of as a complete operating system that you would find on a smartphone or tablet, or it can be a small part of an operating system that is built to run applications as we saw from BlackBerry on OS 10 devices. Most of all, Android is familiar to about two billion people and has a huge ecosystem of software, devices, accessories and support staff. You never abandon something this successful — you build on it instead.
Fuchsia will probably replace the part of the software you don't see; the part that makes the hardware run and lets you tell your phone to do something when you tap the screen or talk into the microphone.
Right now Android uses the Linux kernel and a handful of utility programs written to work with Linux. Linux is great in many ways. It's built to work with almost anything hardware-wise, has a huge community that contributes and makes every version better than the last one, and will be around a lot longer than any hardware you buy today that uses it. Chrome is mostly the same way. Its's a bunch of user-facing services and utilities that run atop the Linux kernel. So is Android Auto, and Android TV, and Wear OS.
But Linux doesn't "belong" to Google and it wasn't designed specifically for mobile hardware. These are two things Google wants and eventually will need in order to continue to compete.
Google needs a mobile operating system built from the ground up at every level designed for 2018. It has to be lean and easy on resources, be able to compute quickly without taxing the chips inside our phones, and it has to be able to instantly respond to all the ways we can "talk" to it like touch, mouse and keyboard, or voice. And it has to do all of this while still being the same user-friendly Android we already know and still run the millions of applications written for Android.
In short, Fuchsia is replacing Linux and parts of Android (and probably Chrome, Android TV, Android Auto, etc.) with something that works better for Google's purposes. The user interface — what you and I see on our phones or Chromebooks or watches — has nothing to do with this part of the operating system. Besides, Fuchsia is too hard to spell.
Benefits of the change
As mentioned, Google wants software they have more control over and that was designed to be lean and fast on the relatively low-end hardware we see in mobile products. But there are two other very important benefits from moving to a custom operating system, and this time we do get to see them.
Developers will be able to use more current programming languages to write applications. We're already seeing this with programming tools like Dart and Flutter making their way to Android, and any new OS is certainly being written with modern programming tools in mind.
There is nothing wrong with programming in C or Java. Both languages are very robust and can make any hardware do anything. But that also means they are designed to do a lot of things a mobile app developer doesn't need, and this can make them a little cumbersome to learn and use. An Android app developer doesn't need his code to communicate directly with the CPU using machine code. But an app developer does need access to easier and more efficient ways to have smooth UI transitions or scalability for different screens. C++ is great for powering a robot, but Flutter is great for building a great app interface. Letting developers leverage tools that help make better apps means we get better apps.
These new tools combined with a unified bottom layer of software across all devices means one app can work everywhere. That's great, but Android already lets one app work everywhere, and to be frank, that means apps mostly suck on any device except a phone. Different size screens need different user interfaces, and most developers only code for a phone-sized one because it's not easy to make an app look great everywhere.
That will change with tools like Flutter and that's our second benefit. Right now it's difficult to build an Android app that works on a small 5-inch display but transforms to take advantage of a 12-inch display. It can be done beautifully — see the Gmail app for an example — but the work involved usually puts developers off the idea. If the tools would let a developer define a few different ways to use the full display to give us the right amount of information with just a few steps, most developers would do so.
Fuchsia demo installed on the Google Pixelbook.
This is what Fuchsia looks like on the Pixelbook. Developers can easily define what goes into the smaller content fields, what is used as a pleasant background, how things are laid out and how much content we need to see with just a few steps. Right now there are only examples and demos, but those give us an excellent idea of what to expect. Compare it to Fuchsia on a phone-sized display below.
Notice the similarities, then notice the differences. This is how one piece of software, in this case, a simple user interface or "home" app, can be changed to perform on two different size displays. This is what Android in its current state is lacking. This is what we need to happen. This is why Google — and we — want Fuchsia to become a real thing.
Nothing is final, everything can change
As mentioned at the top of this article, we've built this on a mixture of rumors, source code uploads, tidbits of insider information, and a dash of imagination. Google has said nothing about any future where Fuchsia is a reality.
That's important because this is a HUGE undertaking. It's even bigger than creating Android in the first place was because much of it involves coding for the bottom layer instead of depending on existing software. Android was built atop Linux, iOS was built atop BSD, Fuchsia is being built from the ground up. It will take a few years until we could see a consumer version or even a version for the public to test that's not just a proof of concept demo. This is hard work that will take thousands of hours to finish.
I believe that Google does have plans for Fuchsia and it's not just a pet project of some talented developers or something Google will start and never finish. I'm paying close attention to all of this, not just because it's how we make our living, but because we're both interested and amazed at what might develop from the project. We'll continue to revisit this space and add information as it becomes available, but for now, there is mostly educated guessing and plenty of wishing involved.
Android Central Newsletter
Get instant access to breaking news, the hottest reviews, great deals and helpful tips
"Google wants software they have more control over" This is enough for me to not want to ever go anywhere near anything running it.
I want Google OUT of my Android phones as much as possible (and the EU fine is a very good step in that direction), not the other way around.
No one is stopping you. By all means go compile and build your own Android and make it exactly how you want it. Have fun using Android with Google "OUT" of the picture...that's not the Android that most people want to use.
Everything that makes Android good is thanks to Google. Without Google, Android would be just a husk of an OS, just a step above a dumb phone.
What the hell? Umm no Google means no Android and how it is today and rethink the internet A LOT!
Luckily you're in a minority, as people don't want to use an Android that doesn't include Google and no stupid EU fine is going to change that.
Buy an iphone
Thanks, Jerry, for this informative article. I understand Fuchsia much better and am excited to see where they take this.
I had made comment similar to this is a forum last week after the previous articles came out. I was thinking that Fuchsia kernel, Zircon, or whatever it's called will be replacing linux which would allow Google to close up Android more and exerting more control. Finally being able to force OEM's to update to the latest OS. The largest shippers of Android phones typically only offer one major OS update and perhaps a dozen security updates if consumers are lucky. Because of this the general public just hears that Android is lacking in updates compared to iPhones. I think this is one reason a lot of customers won't consider an Android phone.
With The shot across the bow by the EU. it'll light a bonfire under Google to get Fuscia up and running faster than planned. Are they announcing it? Heck no but you can bet dollars to doughnuts everything in Fuscia development has been cranked up to 11. If this keeps up with The EU there are two very likely outcomes. One Fuscia goes full bore and we have a New os to replace Android in 2 years. The other is to do a China and pull out of the EU. I wouldn't put it past them to do both.
You do realise that it's only the Linux kernel that's being replaced eventually not Android as whole right?
Fuscia was in response to the Linux kernel Java. From a functional standpoint it would be Android. As to represented this would be a new os. Having now gone closed source.
The EU fines is not due to Android itself, is because Google is leveraging the dominance and monopoly of Android and strong arming hardware manufacturers. This revision to the OS will not stop the EU if Google didn't change their practices.
The "Kotlin" word is nowhere in this article, hopefully, because the article is missing more than it contains...
Remapping \ redesigning \ improving the original Linux kernel for mobile deployment is a wise thing. Something light weight, efficient, robust with self healing properties etc etc etc. As a hobbyist programmer - I've seen good coding attempts go wrong. Each task has a more efficient way of coding style - basically none are the same. Modularity, reuse coding, looking for bottlenecks within your layout or design, designing for backwards compatibiliy. All very hard to do efficiently and it takes a good 'Architect' team to master. Kind of like designing databases - learning to take them to 5th Normal Form and back again - repeat - repeat again. Pain in the ass - but you will gain a new perspective. Time to get out of the rabbit hole...
Think of the possibility to multi boot the two OSs on the same device hardware!
Android/Fuschia Chrome/Windows/Fuschia/Linux Chrome/Android/Fuschia
Get instant access to breaking news, the hottest reviews, great deals and helpful tips
Thank you for signing up to Android Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.