One missing Google Docs feature has a pretty easy workaround

There's a peculiar dissonance in Google's product strategy: the company will happily ship experimental AI features to Docs with remarkable speed, yet a simple dark mode toggle remains conspicuously absent from the web client. The Engadget piece (https://www.engadget.com/2273343/missing-feature-google-docs-easy-workaround-dark-mode-extension/) documents the workarounds users have adopted—extensions that force dark rendering, browser flags that invert colors, and custom CSS injections. Each of these is a small act of rebellion against a platform that simply refuses to meet a basic user expectation. The deeper story here is about how feature fragmentation reveals organizational priorities. Dark mode isn't a novelty; it's an accessibility staple for millions who work at night or suffer from light sensitivity. Google shipped it to mobile, where it arguably matters less for extended writing sessions, while leaving the desktop web experience—where most serious document work happens—in a glaring white void. That inversion suggests the feature isn't being deprioritized because it's hard, but because it's invisible to the product metrics that matter internally. What's telling is the ecosystem that has grown up around this gap. Extensions like Dark Reader and Google Docs-specific dark mode tools have become quietly essential utilities, effectively serving as unpaid product development for Google. This is a recurring pattern across the tech landscape: platforms create vacuums, and third-party developers fill them. Sometimes that's a sign of healthy extensibility; more often, it's a symptom of neglect. When users have to install a separate tool just to change a color scheme, the platform has failed at the basics. The irony is that dark mode is one of the most requested features in Google Docs' history. It's a textbook case of a low-effort, high-visibility win that the company has left on the table for years. As the source notes, the workarounds are "pretty easy"—which only sharpens the question: if it's so easy for users to hack together, why hasn't Google done it natively? Until they do, the extension ecosystem will keep cashing in on Google's inertia, and users will keep wondering why a document editor in 2025 still needs a third-party patch to be comfortable at night.