For years now, we’ve been watching and waiting as Google has gradually developed their Fuchsia operating system from the ground up. Now evidence has appeared pointing to Google’s Fuchsia OS getting its first — and second — proper release.
Expand Expanding Close
Over the course of the past few years, Google’s Fuchsia team has developed support for quite a few devices that seem to line up with known Made by Google hardware. In some cases, those devices appeared in Fuchsia’s code long before they were announced to the public. Looking ahead into 2020, keeping that close relationship in mind, Fuchsia has already laid the groundwork for two more potentially Made by Google devices, codenamed “Nelson” and “Luis.”
In software development, and especially Google’s development cycles, there’s usually a point where the developers “eat their own dogfood” or use their own work, before letting normal users try it. It seems that Google’s long-in-development Fuchsia OS may finally be reaching this “dogfood” stage.
Yesterday, on our Alphabet Scoop podcast, our Stephen Hall dropped a mini bombshell that a Fuchsia tablet is rumored to be in the works. We dug in a bit deeper and found that the truth may be more complicated than that.
Early this year, it was discovered that the first Chrome OS tablet with Qi wireless charging was being developed under the codename “Flapjack.” Fast forward to today, it appears Chrome OS won’t be the only operating system this device supports, as Google’s Fuchsia OS team is also looking to support the “Flapjack” tablet.
Over the past two years, we’ve closely followed the development of Google’s Fuchsia OS and the various hardware products it supports. Thus far, these products have almost all been Made by Google devices like the Pixelbook and Nest Hub, used simply as testbeds for Fuchsia on various form factors. But if Fuchsia is to ever succeed, Google will need to partner with other companies on developing their own Fuchsia-based hardware and software projects.
This week in Fuchsia Friday, we take a look at the various Google partners that have looked into Fuchsia OS, including familiar names like Samsung and Sony.
With all the hype around the Pixel 4 this week, we thought it might be good to look at some of the other things Google might have in the Made by Google hardware pipeline. A new hardware prototype, codenamed “Visalia,” has popped up in the Fuchsia OS source code, which could be yet another Google Home device.
Following along with the development of Google’s Fuchsia OS, it has become clear that it will be capable of running both Linux and Android apps. Chrome OS can also do both of these things, and that’s no coincidence, as the Fuchsia team has opted to use some of Chrome OS’s developments for their own benefit.
We’ve all been watching and waiting eagerly for the official launch of Fuchsia, Google’s in-development OS for anything and everything, but the company has barely even acknowledged its existence thus far. Despite this lack of publicity, Fuchsia has marched on toward its latest milestone—the first “release candidate.”
Our avid readers know that we follow Fuchsia, Google’s in-development operating system, closely here at 9to5Google, for both its software and the various device prototypes that Google adds support for. This week on Fuchsia Friday, more details have come to light about Fuchsia’s “Sherlock” prototype, which strongly associate it with the Google Home Hub and suggest a Home Hub “Max” could be in the works. Expand
Expanding
Close
With CES 2019 now in the rear-view, we’re reflecting on the innovations that were on display, including new ways to interact with the Google Assistant. One of these, the Lenovo Smart Clock, may hold unexpected answers for Google’s hardware plans for Fuchsia.
Earlier this week, we reported that just about everything we’ve seen about Fuchsia is now gone, as the “Armadillo” UI has been deleted. In its place, we only have references to what seem, in context, to be three other “shells” or user interfaces which are all kept closed-source by Google. However, one of these, “Dragonglass,” may offer more answers than we initially thought.
With the significant news this week that the Fuchsia SDK and a Fuchsia “device” are being added to the Android Open Source Project, now seems like a good time to learn more about the Fuchsia SDK. Today on Fuchsia Friday, we dive into the Fuchsia SDK and see what it has to offer developers who might want to get a head start on Fuchsia.
In an interesting turn of events this Friday evening, the beginnings of support for the Java programming language has arrived for Fuchsia. Where things get interesting is that this change was found in Android’s code, not Fuchsia’s.
Over the months, we’ve followed a variety of prototypes for Google’s Fuchsia OS, each filling a different niche from Google’s current product line. This week on Fuchsia Friday, we look at the latest prototype, Sherlock, and some of the possible form factors it could take.
Things have been relatively quiet in the Fuchsia scene as of late, but development work has not ceased. Today on Fuchsia Friday, we take another look at Fuchsia’s device prototypes as found in its source code, including a brand new one.
Many of you have seen the reports claiming Fuchsia will replace Android within the next 5 years and have shared understandable concerns about how Google can so swiftly replace such a core piece of their ecosystem. This week, we take a look at where Fuchsia might fit in and how Google could make it a smoother transition. Expand
Expanding
Close
Reports emerged yesterday about the future of Fuchsia OS, including a five-year plan to replace Android. Today, we’re going to take a closer look at one interesting aspect of the report that has sparked keen interest, specifically where Fuchsia will stand on user privacy.
We all know Google is in the business of analytics, whether it’s as a service to help web developers or to help improve the relevance of ads you’re shown. Android developers even have the option of putting Google Analytics into their apps to better understand their users actions and decisions.
It comes as no surprise to me that Google’s Fuchsia Team has decided to build analytics directly into the operating system.
This week in Fuchsia Friday, we take a look at how Fuchsia will appeal to web developers and an interesting look at Fuchsia possibly being used outside Google.
This week we talk all about Fuchsia. Our Kyle Bradshaw has been tearing apart Google’s in-the-works operating system for several weeks now, and we’re summing it all up in about an hour.
Alphabet Scoop is available on Google Play, Google Podcasts, iTunes and Apple’s Podcasts app, and through our dedicated RSS feed for Pocket Casts and other podcast players.
Last time on Fuchsia Friday, we dug into two prototype devices that Google is developing to run on Fuchsia, and mentioned that there’s a third “device” in the works. Today we’ll take a look at Machina, Fuchsia’s built-in emulator.
Since we first heard about it in 2016, we’ve pretty much known that Fuchsia will run on a variety of devices — from phones to traditional laptop/desktop computers. There’s more to it, though. In the past few months, Fuchsia’s Zircon kernel has picked up support for a handful of new devices, including two codenamed Google projects, each expanding the reach of what Fuchsia will run on.
Thus far in the Fuchsia Friday column, I’ve been Fuchsia’s number one fan, and each week I hope my enthusiasm shines through. This week, however, I’d like to address something in the work-in-progress OS that has me worried, albeit not a problem that’s unique to Fuchsia in any case.
In the last few days, some of you have noticed that Android is gaining some of the same kinds of features and concepts we’ve discovered are coming in Fuchsia. Let’s take a few minutes to dig into each of them and what they mean as a whole for the two OSes.
With all the developer excitement following Google I/O this week, we’re keeping in theme with a developer-oriented Fuchsia Friday.
Earlier this month, Fuchsia gained its first official screenshot tool! No more looking ridiculous by taking a photo of a screen. With this change, I figure now is the perfect time to give a closer look at some first impressions of Fuchsia’s user experience.
This week on Fuchsia Friday, we look at one of the most requested features of Fuchsia and how it might be possible.
This week on Fuchsia Friday, we take count of Fuchsia’s development team and highlight some of its members. The backgrounds of Fuchsia’s contributors are widely varied, including those from RedHat, FreeBSD, Danger, BeOS, iOS and more. Let’s take a look at some of these, and have fun speculating what it might mean for the behind-the-scenes OS that is Fuchsia…
Fuchsia Friday is back with your fix of Fuchsia information. This week, we’re looking at how Fuchsia handles graphics differently and what that might mean for gaming and VR.
This week on Fuchsia Friday, we get to take a look at our most requested topic: Maxwell, the smarts behind Fuchsia.
When describing the organization of Fuchsia code, Google uses a “layer cake” metaphor. Fuchsia is the name of the project as a whole and of the finished product (we presume), but under the hood there are 4 distinct layers that it’s divided into. This week’s Fuchsia Friday details each layer and what we know about them.
If something isn’t growing, it’s dying. With the slew of neglected devices not receiving Android Oreo, it could be argued that the update system is one of Android’s fatal flaws. Fuchsia is trying to be different. This week in Fuchsia Friday we look at Fuchsia’s ambitious update system.
Earlier this week, Google’s new cross-platform mobile app framework Flutter hit Beta. To celebrate that, let’s take a closer look at what Flutter is doing for app development today, and how it’s preparing developers and users alike for Fuchsia.
This week in Fuchsia Friday we look at the bigger picture. Google is making Fuchsia fundamentally different from systems of the past, especially learning from the challenges the company has encountered with Android. But now that we’ve taken a few weeks to describe some of its more important elements in detail, let’s take a step back and look at the big picture. Let’s check out the building blocks and terminology that Google uses to describe Fuchsia’s “modular” design.
With Fuchsia, Google’s upcoming OS for phones and computers, comes a chance to revamp and rebuild existing Android experiences and build them deeper into the operating system. In this week’s Fuchsia Friday, we’re looking closer at how Fuchsia has replaced the app drawer, and what seems to be an exciting reimagining of Instant Apps-like functionality.
Two weeks ago, we learned about Fuchsia’s Stories and Modules, and how they will help us better organize our time, tasks, and ideas. This week, we’re looking at the idea of ‘entities’, Fuchsia’s attempt to catalog the digital world to be read by Assistant. Entities are also part of the glue that holds disparate “modules” together into one coherent Story.
Last Friday, we took a look at how ‘modules’ in Google’s forthcoming Fuchsia OS come together to make ‘stories’. As we learned last week, a story is one or more apps working together to help you complete a single task. Fuchsia, for the uninitiated, is also designed to allow for quick switching between devices by saving your Stories to your personal ledger.
This week, we’re learning more about Ledger and how it helps Fuchsia tell your story.