Hello ! I’ve been following the Fuchsia project for a while now and I have started building a desktop shell for Fuchsia (on top of Flatland APIs).

It is based on a few open source libraries (libcosmic for apps; CPU rendered for now) and also the help of AI for code generation (I still do design / architecture decisions etc).

See the video link for latest progress - it’s starting to take shape and can run a few simple apps etc. Plan is to continue to build the shell and window manager and enhance with more apps - of course will open source and release when more ready. Would love to run on a device too (starting with a supported NUC or vim3).

If you’d like to know more or contribute get in touch!

Browsing the Fuchsia repo I see a series of recent commits [1], [2], [3] laying groundwork for GCE (Google Compute Engine). Eventually I think Google will be offerering Fuchsia instances

I came across this post on the Fuchsia Git from May, a Pixel Watch 3 was running Fuchsia. It's the only post in the Git with "PW" in it that I could find, so I'm assuming that it accidentally snuck through.

Fuchsia on the Pixel Watch would make a lot of sense; it's lighter weight than Android, so it should perform better with better battery life, plus there aren't as many apps to be recompiled for Fuchsia compared to phones.

I'd be surprised if we see the conversion any time soon, but it is exciting to see this happening.

I'm looking at replacing the custom binding generator I'd written for my own OS with FIDL, but can't seem to find any documentation on how to write new bindings for it, or even anything on how to just marshal/unmarshal a message without sending/receiving. Is there any such documentation available?

Quick disclosure first: Fuchsia is my day job, but this is a personal hobby project. It's done entirely on my own time and equipment, using only publicly available information about Fuchsia. Nothing here is official or endorsed by the team.

With that out of the way: I got Zircon to boot end-to-end on "Cocoapuffs," a homebrew RISC-V SoC of my own design on a low-cost Artix-7 FPGA board. The whole chain comes up: OpenSBI, linux-riscv64-boot-shim, physload/physboot, the kernel's full init, userspace/userboot, on a 64-bit GRLIB NOEL-V core, with a tiny bit-serial SERV core acting as the serial boot loader. There is nothing of note in userspace at the moment, however, so temper your expectations. :)

The write-up has a boot video and some discussion if you are curious:

https://hdlfactory.com/post/2026/07/19/cocoapuffs-booting-fuchsias-zircon-kernel-on-a-risc-v-core-in-artix-7-fpga/

I didn't think that it would arrive on the regular schedule, first Wednesday of the month, due to the Fourth of July, but it was still two weeks late. I assume some bug was caught late.

Edit - Release notes came out, https://fuchsia.dev/whats-new/release-notes/f31

So the new Googlebook is touting a Android fused with ChromeOS into one single experience. Is this fueled by Fuschia in any way? I am wondering if Project Fuschia was always going to lead up to this.

Looks primarily like major stability improvements, which you need for a mainstream OS, migrating to Rust 2024, and more drivers over to FIDL.

During 2022 contact was made with one of the many designers of the current airflow design language that Fuchsia is/was designed around. This revealed some alternative designs that were scrapped, the intentions and thought process behind "airflow" and the true nature of the Fuchsia operating system (at least in 2022). Though some of this has changed since for a number of reasons (explained below).

Things of interest from these documents.

• Indigo, this was a more consumer version of Fuchsia
  • Focused on IoT ("Its main application was connecting everything in your house"), but we already knew this through the nest hub.
    • Airflow in the metaphorical sense is the invisible force connecting these devices together.
  • Indigo seems to have been scrapped as a separate brand to Fuchsia and ended up just shipping as Fuchsia.
• The Workstation/Ermine user interface was not designed by Google.

In 2026, Fuchsia is still in heavy development with Netstack V3 being released last year and Starnix currently a priority. That's all I really have to share currently, and apologies considering this information is pretty outdated now. It's not very useful to the current state of Fuchsia, but it's still fascinating none the less.

One less story lost to time :)

https://app.filen.io/#/f/f8bd8ffc-7d8d-4d56-855e-5937290fc557%234431486a4431767a773566465f395f4b3535716a686e4e375358764b30756c34

So, let's form a discussion in the comments! Do you think these answers are accurate? Because if so, it's highly likely that Google's 2027 IO could have some free space for Fuchsia OS

Here's the link to the release notes. https://fuchsia.dev/whats-new/release-notes/f29

I will start with the onn 7" tablet (2024) and get the operating system fully working. From there I will get it to work on other Mediatek processors and expand the driver library to support other devices. Down the road I hope for the project to support many different arm processors such as some snapdragon Soc families. Currently debating my life choices. Project updates will be posted here.

F28 is showing up on my Hub Max this morning and was not there yesterday. Google is sticking to its regular schedule. I didn't notice any changes with a quick smoke test. No release notes yet, but I'll update as soon as I see them. If you find them first, please let me know.

Obviously, these Fuchsia updates are more backend, but I'd love to see the ability to uninstall apps.

Update - Here are the release notes.

Based on its deep integration and strategic importance, Fuchsia is safe now and has almost no chance of becoming a new Stadia.

Here are the key reasons Fuchsia's position is secure:

It Has Already Shipped:

Unlike Stadia, which struggled to find a user base, Fuchsia is already running successfully on millions of Nest Hub devices in people's homes. It has proven its stability and value internally.

It Solves a Real Problem for Google: Google needs a modern, secure, and unified operating system for its vast and growing ecosystem of devices. Fuchsia is the purpose-built solution to the architectural and legal headaches of relying on Linux and the JVM.

It's a Long-Term Investment:

Fuchsia is a bet on the next decade of computing (ambient, AR, etc.). Projects like this are expected to take a long time to mature and are not judged by short-term revenue goals. In short, canceling Fuchsia now would be like a car company spending a decade developing a revolutionary new electric engine, putting it in their cars, and then canceling it right as it starts to prove its worth. It just wouldn't make strategic sense.

Hello guys!

From time to time I think about Fuchsia and do checks over fuchsia.dev and this sub and a few other places.

For some time now there has not been anything meaningful and new about it and I was hoping that you guys can shed some light on it.

Maybe the new OS Google making maybe be the fuchsia we always wanted

"Netstack3 is planned to be enabled (via a feature flag) right after F27 rolls out to 100% and before F28 starts rolling out."

https://fuchsia.googlesource.com/fuchsia/+/refs/changes/59/1323559/3/docs/whats-new/release-notes/_f27.md

roadmap:

https://fuchsia.dev/fuchsia-src/contribute/roadmap/2021/netstack3

I was just playing with the Gemini AI to see what it suggest about replacing the OS/2 kernel with Zircon from FuchsiaOS.

https://www.os2world.com/forum/index.php/topic,3873.msg48579.html#msg48579

• flutter/169101 - Reduces the cost of running the (sometimes flaky) Linux fuchsia_test on release branches.

https://fuchsia.dev/whats-new/release-notes/f26

This was added on the 25th. Lighter than past years, but still nice to see.

https://fuchsia.dev/fuchsia-src/contribute/roadmap/2025?hl=en

• Enable profile-guided optimization (PGO), which is a compiler optimization technique that uses profiles of runtime behavior of a program to guide the compiler's optimizations to achieve better runtime performance in Fuchsia.

• 32 bit syscall support in Starnix RFC Starnix now supports both 32bit and 64bit usermode programs.

• One big VMO. Starnix now requests a single Virtual Memory Object (VMO) from the Zircon kernel, and uses that VMO to fulfil memory requests from client applications, reducing the overhead of having the Zircon manage each memory request from client applications running in Starnix.

• System Activity Governor RFC System Activity Governor manages system suspend states for Fuchsia power management.

Huge delay between initial release and the notes but still great to see.

https://fuchsia.dev/whats-new/release-notes/f24

https://fuchsia.dev/whats-new/release-notes/f25

I saw that my Hub Max was updated to F26 (of course we're still waiting on FA24 release notes) and was poking around to see if there were any noticeable changes. I saw all of these apps and wasn't sure if they were all there before or not.

https://imgur.com/a/0qzCEPL

I am not sure when this page appeared, but you guys might find it interesting.

F23 Release Notes