Google is preparing one of its most ambitious software shifts in years. The company has confirmed that Aluminium OS, a new operating system designed to unify Android and ChromeOS, is on track for release in 2026 — a move that signals a major transformation in how laptops, tablets and smartphones will work together within the Google ecosystem.
The announcement, reinforced during industry events including Mobile World Congress 2026, confirms long-standing rumors that Google wants to eliminate the divide between its mobile and desktop platforms. According to company executives, Aluminium OS aims to create a more seamless experience between phones and computers, powered heavily by artificial intelligence.
Rather than maintaining separate operating systems, Google is developing Aluminium OS as a platform that merges ChromeOS capabilities with Android’s foundation. The goal is to allow apps, services and workflows to move fluidly across devices, responding to growing user expectations for continuity between screens.
Industry reports indicate the new system will be built directly on Android technology while incorporating desktop features traditionally associated with Chromebooks, including window management and productivity tools.
Sameer Samat, president of Google’s Android Ecosystem, confirmed that development remains on schedule for a late-2026 launch, emphasizing that advances in AI and changing computing habits are driving the transition.
ChromeOS isn’t disappearing, yet
Despite speculation that ChromeOS could be phased out entirely, Google has clarified that existing devices will continue to receive support. The company is pursuing what analysts describe as a gradual evolution rather than an abrupt replacement, ensuring compatibility for schools, businesses and consumers already using Chromebooks.
This dual-strategy approach reflects Google’s need to balance innovation with stability. ChromeOS remains widely used in education and enterprise environments, meaning a sudden transition could disrupt millions of users.
Discussion about this post