Google didn’t announce a plan to replace the operating system. It didn’t need to. Over the past decade, Chrome has quietly absorbed the functions that once required dedicated software - file editing, video calls, design tools, code environments - until the line between “app” and “website” stopped meaning anything useful to most people.
This isn’t a Chrome OS argument. That product has its own limited story, mostly confined to classrooms and budget hardware. The bigger shift is happening on mainstream Windows and macOS machines, where users are spending the overwhelming majority of their computing time inside a browser window. Figma runs there. Notion runs there. VS Code has a browser version. Linear, Vercel’s dashboard, Supabase, Google Workspace - all browser-native, all perfectly capable, none requiring an installer.
The Electron Problem Made This Inevitable
For a while, Electron apps were the answer to cross-platform desktop software. Wrap a web app in a Chromium shell, ship it as a native binary, done. Spotify, Slack, Discord - these are Electron apps dressed up to look like system software. The disguise worked well enough, but it also made something obvious: the underlying technology was always the web. Electron was never a bridge to native computing. It was a sign that the web had already won, and developers were just managing perceptions.
As browsers became more capable - with access to local file systems, background sync, push notifications, and hardware APIs - the Electron wrapper became harder to justify. Why ship a 200MB desktop app when a Progressive Web App can install in seconds and behave almost identically?
The One Thing the Browser Still Can’t Touch
Performance-sensitive workloads. Video editing, 3D rendering, machine learning inference, audio production - these still require native execution, direct GPU access, and memory management that a browser sandbox can’t provide. DaVinci Resolve is not moving to the web. Neither is Ableton.
But that carve-out is narrowing. WebGPU is a real API now, shipping in Chrome and Firefox, giving web apps direct access to GPU compute. Adobe already runs Photoshop in the browser. The ceiling is rising every year.
What’s less clear is whether users want the browser to win this completely. There’s something being lost when every tool lives inside the same tabbed interface - not nostalgia for installer wizards, but the sense that software with a distinct presence has a different relationship to the work you do in it. Whether that distinction survives the next five years of browser capability improvements is genuinely hard to call.