Fuchsia

Our avid readers know that Google is working on a third operating system, Fuchsia, that has the potential to eventually replace both Android and Chrome OS, being designed for laptops, phones, and even smart home appliances. One thing all of these gadgets have in common is Bluetooth capability. It seems Google is already testing the new OS’s Bluetooth capabilities by quietly bringing devices running Fuchsia to an official Bluetooth testing event.
In a Thanksgiving surprise, a new code change has revealed the first Android smartphone to be used as a testbed for Fuchsia, Google’s in-development operating system for devices of all kinds. The bigger surprise — it’s a Huawei.
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.
Amidst the announcements from yesterday’s Made by Google Event, we got a variety of details on the hardware for each of Google’s upcoming products. One of those, the Google Home Hub, may have outed itself as the latest Fuchsia OS device.
Back in January, we took a precursory look at the in-development, cross-platform Xi code editor that then-Googler Raph Levien was building and how it related to Google’s Fuchsia OS. Levien has since left his position at Google and gave an update yesterday on how that will affect Xi’s development going forward.
Google has long been at work trying to get their Chromium web browser up and running on their upcoming, work-in-progress Fuchsia operating system. We now get to see the first fruits of that effort, with a hands-on look at Chromium for Fuchsia.
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.
Dart, the programming language powering Flutter, Google’s cross-platform app development kit, and one of the primary languages used in Fuchsia OS, has officially reached version 2.0.0.
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’ve been very closely following the development of Google’s Fuchsia OS with the publicly available information in both the source code and code review. While this is often all we need to take a guess at how Fuchsia is progressing, we almost never see what happens behind closed doors at Google. A new report offers insight on Google’s plans for the open source OS, including upcoming devices and ambitions to replace Android.
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.
Google is actively developing a YouTube app for its fledgling Fuchsia operating system, according to evidence we found in its source code. On a proposed change related to a Tic-Tac-Toe demo game being created for Fuchsia, Googler Larry Landry posted a link that appears to be for code from a private, in-development “YouTube Player”.
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.
Sometime in late May, Fuchsia, Google’s in-development OS for mobile (and more), added a loose connection to AOSP in the form of new ‘projects’ in their Gerrit source code management hub, but now the code is being used and we can see what it’s actually for.
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.
With I/O just around the corner, many are left wondering why Fuchsia doesn’t seem to be present. While that does, at first, seem to be the case, the truth is a little more complicated.
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.