brighter workshop
StandardsRead the notes
Menu

PatternsField note / 2026

Google Opens Gemini and Search to Outside Apps as Agents Take Over Discovery

A new developer platform lets businesses plug services directly into Gemini and Search, a move that could quietly rewrite how people find and use apps.

Google announced on October 28 a developer platform that lets businesses bring their services directly into Gemini and Search, according to the company. Instead of a user opening an app, searching inside it, and completing a task there, the service itself becomes reachable from inside Google's own products. The company frames this as a response to AI agents reshaping the web, though it did not disclose which businesses are participating first or when the platform opens broadly.

For more than a decade, discovery has worked through app stores and search results that point outward, to a website or a downloaded app. This platform points inward instead, pulling the service into Gemini and Search as a built-in capability. That is a structural change, not a cosmetic one. It suggests Google sees the browser tab and the app icon as a weaker front door than a conversational interface, and it is building the plumbing to make the conversational interface the front door instead.

The context is a broader industry shift toward agents that act on a user's behalf rather than simply returning links. Google's own framing ties this platform to that shift explicitly, positioning Gemini and Search as surfaces where an agent can complete a task using a third party's service without the user leaving the conversation. Google did not disclose technical details of how services integrate, what data businesses share back, or what review process governs which apps qualify, so the shape of that plumbing remains unconfirmed.

For builders, the open questions outnumber the settled ones right now. Teams integrating with the platform will need to check how much control they retain over branding and user experience once a service is embedded in someone else's interface, since Google did not disclose specifics on that front. Accessibility also becomes a shared responsibility rather than a solo one: a service rendered inside Gemini inherits whatever interaction model Google builds, which means keyboard navigation, screen reader behavior, and error handling may no longer be fully within a developer's own hands. Analytics and attribution, too, get murkier once discovery happens inside someone else's agent.

The visual and functional result, if the platform works as described, is fewer standalone destinations and more embedded moments, a ride booked or a reservation made without a separate app ever opening. That replaces the current pattern of app switching with something closer to a single continuous surface controlled by Google. Whether businesses accept that trade, less direct control in exchange for placement inside Gemini and Search, is the unresolved part of this story, and Google's announcement does not settle it.

What Google confirmed is the opening of the platform itself. What it left unsaid, participation terms, rollout timing, integration mechanics, is exactly what builders will be pressing the company to clarify next.

Related guides

Primary references