Google Aluminium OS Leak: Desktop Shell Confirmed, Apps Still Missing

Ahead of Google's Android Show: I/O Edition event today, leaker Mystic Leaks published a 16-minute hands-on video of Aluminium OS on Telegram, one of the most detailed public looks yet at the Android-based platform Google intends as a long-term successor to ChromeOS. The Google Aluminium OS leak confirms the company has built a functional desktop shell. It also shows, in plain view, what's missing.

The build runs inside the UTM emulator on a MacBook Pro, so the footage reflects direction more than final hardware behavior. With that caveat stated: virtual desktops, freeform window resizing, desktop folders, a Task Manager, a bottom app dock, and an adapted Quick Settings panel are all visible, according to Android Authority. The leaker's own read is that Aluminium OS is essentially plain Android with desktop additions closer to an upgraded Samsung DeX than to Windows or macOS.

The central question this footage raises is not whether Android can run on a laptop. It's whether the apps on that laptop will ever feel like they belong there.

What the Google Aluminium OS leak video actually shows

The home screen will look immediately familiar to anyone with a Pixel. A bottom dock with an app drawer button, a Google Search bar, a Play Store icon, a pre-loaded folder of Google apps setup runs through the same wizard used on current Android phones, Android Authority reported today.

The desktop-specific work is genuine. Compared to Android 16's standard desktop mode, Aluminium OS has a taller taskbar and a revised menu bar showing battery level, Wi-Fi status, and active background processes. Window controls minimize, maximize, close sit in the upper-right corner. Windows can be freely resized or arranged full-screen, per NotebookCheck. These aren't phone-layout stretch jobs. Google has made deliberate choices for large-display use.

The Quick Settings panel pulls in from the side as a compact vertical overlay rather than dropping from the top a layout better suited to wide displays, NotebookCheck noted. The footage also includes a "Link to iOS" integration for Apple iPhone connectivity, according to Android Authority.

One detail worth flagging: the Play Store and Chrome browser extensions appear in the same environment, with Chrome showing an extensions button alongside the address bar, per Android Police and NotebookCheck. Fresh visual evidence of a hybrid app model Android apps and the Chrome extension ecosystem under one roof.

What Aluminium OS actually is, and why the app gap is the real problem

Aluminium OS is not a new operating system built from scratch. Court documents filed in Google's search antitrust case describe it as "ChromeOS built on the Android stack" rebuilding ChromeOS's foundation using Android's Linux kernel and existing frameworks, per 9to5Google. System strings visible in the leaked footage refer to the OS as "Android 16," making the lineage explicit, Android Police reported.

The pitch behind an Android-based foundation is straightforward. A unified core means Google maintains one kernel rather than two, and can ship platform updates to Pixel phones and Chromebooks at the same time, according to a single architectural analysis from ChromeReady. That analysis also claims the architecture eliminates ARCVM, the virtualization layer that makes Android apps feel heavier on current ChromeOS than native software though that specific claim has no independent corroboration, and should be read accordingly.

What the leak makes harder to wave away is the app problem. Even Google's own applications in this build appear to be web versions wrapped in windowed containers, not mouse-and-keyboard-optimized software, Android Authority reported. Chrome and first-party Google services are treated as first-class citizens in Aluminium; third-party user apps are not, The Verge noted.

This is the DeX problem at scale. Samsung built a credible desktop shell for Galaxy devices years ago; DeX remains a curiosity rather than a laptop replacement because the apps never followed. Google starts from a stronger platform position, but the structural challenge is identical: developers don't optimize for a platform that isn't shipping, and the platform struggles to ship until developers have optimized for it.

The antitrust judgment adds a complicating wrinkle. The final ruling in Google's search case exempts ChromeOS and its successors including Aluminium OS from restrictions that would otherwise prevent Google from making deals requiring its apps to be prioritized on devices, per 9to5Google and The Verge. That gives Google more latitude to default its own software on Aluminium hardware than it has on standard Android. Useful for guaranteeing a baseline experience. Not a substitute for a third-party app ecosystem.

Google can solve the technical merger. The app gap is a developer adoption problem, and a polished taskbar does nothing to close it.

Who should pay attention now, and who can wait

The timeline from court documents is the most reliable guide available. Commercial trusted testers get access in late 2026; a full release isn't expected until 2028. Enterprise and education the sectors where Chromebooks have their strongest foothold are targeted for 2028, not the earlier window, per The Verge and 9to5Google. A leak in May 2026 does not move those dates.

Hardware compatibility is an open question with real stakes. A Google witness in the antitrust proceedings confirmed that some Chromebook devices will not support Aluminium OS, though no chip requirements or specific estimates were given, The Verge reported. ChromeOS remains supported through at least 2033, with the full phase-out timeline set for 2034, meaning most current Chromebook users aren't facing a forced transition anytime soon, according to 9to5Google.

For consumers on a recent Chromebook: nothing changes today. Wait for hardware compatibility disclosures; that's the actual decision point.

For IT administrators and educators managing device fleets: 2028 is the relevant date. The questions worth putting to OEMs now are about migration paths and device support, not feature lists.

For developers building for ChromeOS or Android: the hybrid Play Store and Chrome Extensions model is the most consequential signal in this leak. Whether those two ecosystems will be treated equally when Aluminium ships on real hardware is still an open question.

What happens next

The leak settled one thing: Google has built the shell. The Google Android desktop experience visible in this footage is functionally real, not a roadmap slide. What it hasn't settled is whether the software running inside that shell will be ready when the hardware ships.

Three signals worth watching at today's Android Show event, and in Aluminium builds going forward: whether Google announces mouse-and-keyboard-optimized versions of its own first-party apps rather than web wrappers, what the company discloses about hardware compatibility for the existing Chromebook base, and how the app model gets framed Android apps plus Chrome extensions as rough equals, or something with a clearer hierarchy. Those answers will say more about Aluminium's chances than any amount of window-management polish.