May 11, 2026
No vote, no committee, just a blog post
In 2020, Google turned a blog post into digital product law. The Prompt API follows the same logic — only this time the model runs on the device while the rules stay with Google.
In May 2020, Google published a post on the Chrome blog announcing that three performance metrics would start influencing search rankings in 2021. No vote, no standards committee — just a post.
What followed were product teams rewriting roadmaps, SEO agencies repositioning their services, and Core Web Vitals becoming a permanent fixture in the backlog of any product with ambitions of appearing on Google. Not because anyone decided it was a good idea, but because Google decided it was, backed by 67% browser market share.
The Prompt API follows the same logic: Chrome now allows web pages to send natural language instructions to Gemini Nano, a model that runs locally on the device without any server traffic. Mozilla filed a formal objection at the W3C arguing this fragments the open web, and they're technically right — but Firefox has less than 3% market share, so the fight is legitimate without being relevant.
The detail that's getting overlooked is that using the Prompt API requires accepting Google's Generative AI Prohibited Uses Policy. The model runs on the user's device, but the content rules stay with Google, without the user having signed anything.
For those building products, the question isn't whether this will become standard — the track record suggests it will. The question is when you'll decide what to do with a layer that's already sitting between your product and your user, even though you never asked for it.