Most people reading this have at least one Chrome tab open that they haven’t closed in days. Maybe it’s Notion, Figma, or a Gmail window masquerading as an app. At some point - without any announcement - the browser became the operating system for a significant portion of daily computing. Nobody voted for this.
How We Got Here Without Noticing
The shift happened gradually through Progressive Web Apps, better JavaScript performance, and companies deciding that maintaining separate codebases for Mac, Windows, and Linux wasn’t worth the engineering cost. Electron filled the gap for a while - wrapping web apps in a thin native shell - but Electron apps are famously memory-hungry, and developers have increasingly questioned why they’re shipping a bundled Chromium instance just to run a to-do list.
The honest answer is that the web stack won because of deployment, not because of quality. Pushing an update to a web app means updating one server. Pushing a native app update means trusting that users actually install it, which they often don’t.
Chrome’s Structural Advantage
Google built Chrome with the explicit long-term goal of making the operating system irrelevant. ChromeOS proved the concept worked for a specific market - education, budget hardware - but the real prize was the browser itself becoming the dominant runtime on every platform. As of mid-2026, Chrome holds a majority of global browser market share by most independent tracking estimates. That’s not a coincidence; it’s the product of Google controlling the default browser on Android and spending years making Chrome the performance benchmark that other browsers chase.
Safari on iOS remains a genuine counterforce, but Apple’s tight restrictions on third-party browser engines within iOS mean that even competing browsers on iPhone are essentially Safari underneath. Google doesn’t face the same constraint on Android.
What This Costs Users
The browser-as-platform model trades capability for convenience. Web apps still can’t match native apps for performance-intensive tasks - video editing, 3D rendering, anything that needs sustained GPU access. The gap has narrowed, but it hasn’t closed.
More quietly, it creates a concentration problem. When the browser is the platform, whoever controls the dominant browser controls what the platform can and can’t do. Google’s decisions about API access, ad-blocking extension policy, and manifest V3 restrictions don’t just affect Chrome - they effectively set policy for the web.
That’s an enormous amount of infrastructure to trust to a company whose primary revenue source is advertising.