Google's Connected Apps Platform: Build Once, Live Inside Search and Gemini

Nothing here is sponsored — no affiliate links on this page. Every fact below comes from Google's own announcement of October 28, 2026. We have not tested the platform hands-on — it is a phased US developer preview behind a waitlist — and capabilities described here are Google's announcement claims, not independently verified results.

Google wants your app to live where its users already are — inside Search and the Gemini app — and on October 28, 2026 it opened the door to developers to make that happen. The new Connected Apps Platform, now in preview, lets you build and manage an app for Search, for Gemini, or for both, from one place. It is a genuinely interesting distribution channel. It is also a phased preview, behind a waitlist, with Google reviewing everything — so read this as a door opening, not a launch party.

What launched

The Connected Apps Platform is a unified place to build and manage apps for Google Search and the Gemini app. The key choice it hands developers is simple: target Search, target Gemini, or target both. Instead of maintaining separate integrations for each surface, you build once and choose where your app appears.

The pitch to users is equally simple. Rather than leaving Google's AI tools to open a separate app, people can do things — Google's own examples include designing a flyer in Canva, building a YouTube Music playlist, or ordering groceries — without leaving Search or Gemini. Your app shows up inside the conversation, at the moment of intent.

That framing matters because it tells you what kind of app benefits most. If your product answers a question, completes a small task, or fits naturally into something a user is already asking an AI assistant to do, this is your surface. If your product is a destination people browse for an hour, it probably is not — at least not yet.

How integration actually works

Google offers two integration routes:

• Cloud-hosted MCP server — expose your app's capabilities through the Model Context Protocol, hosted in your cloud.
• Android MCP via AppFunctions APIs — the on-device route for Android apps, through AppFunctions.

After integrating, developers register, test and submit through the Google Connected Console. Once live, the console also becomes the operations view: traffic, latency and error rates for your app inside Google's surfaces. That last part is easy to skim past, but it is the difference between a listing and a channel — you can see whether the integration is actually being used, and whether it is fast and reliable enough to keep users.

One detail worth noting for brand-conscious teams: developers keep their verified brand identity and authenticated accounts. Your app appears as yours, under your verified identity, rather than dissolving into a generic Google answer. For any business that has spent years building a brand, that is a meaningful design choice — and one worth confirming in practice once you are inside the preview.

Who can get in — and when

Here is the part to be honest about: this is a US developer preview, and access rolls out in phases over the coming months via a waitlist. Google has not given a date for broader availability, and has not stated pricing, fees, ranking rules, or data terms. If you are reading coverage that quotes any of those, it is guessing.

There is already real activity on the platform, though. More than 50 Connected Apps are already live in Gemini, and Google has named the next wave: Adobe, Experian, Localiza and Peloton are coming to Search in the coming weeks, while Calm is launching on both Gemini and Search. That is a useful signal about the kinds of partners Google is prioritising first — productivity, finance, travel, fitness, wellness — and about where the early slots are going.

What is actually new here

An important piece of honest framing: Connected Apps themselves are not brand-new. Consumer integrations already existed in AI Mode earlier in 2026 — users have been reaching apps from inside Google's AI answers for months. What is new today is the open developer platform: a public preview, a documented integration path, a console, and a waitlist any developer can join, rather than a set of hand-picked partnerships.

That distinction changes how to evaluate the news. It is not "Google invented apps inside AI." It is "Google is now letting developers in." The question shifts from whether the concept works — it has been live in limited form — to whether the open platform sends meaningful traffic, on fair terms, to developers who are not Adobe or Peloton.

Why a developer should care

First, distribution is the hardest problem most apps have. Getting users to install something new is expensive and getting more so. Appearing inside Search and Gemini, at the moment a user expresses intent, is distribution you cannot buy at any price through an app store listing. If the platform works as described, it is a new acquisition channel — and early channels reward early movers.

Second, MCP is becoming the shared language of AI integrations. A cloud-hosted MCP server is not a Google-only investment: the same protocol thinking applies across the AI ecosystem. Building the MCP route now is work that transfers even if this particular platform disappoints.

Third, the console metrics make this measurable. Traffic, latency and error rates, in one place, means you can treat this like any other channel: measure it, compare it against your other acquisition, and keep it only if it earns its place.

The catches, stated plainly

• Google reviews everything. This is distribution inside Google's products, on Google's terms. Submission is not a guarantee of acceptance, and the review criteria are Google's to set.
• Commercial impact is unproven. No public numbers show what a Connected App listing is worth in users or revenue. The 50-plus live apps prove the plumbing works, not the economics.
• Access is phased and US-first. Joining the waitlist is not joining the platform. International developers, and developers outside the first phases, will wait an unknown amount of time.
• The terms are unstated. Pricing, fees, ranking, and data terms have not been announced. Any business case built today rests on assumptions Google has not confirmed.

What to do now

• Join the waitlist if your app fits a Search or Gemini moment — the phased rollout rewards being early in the queue.
• Map your app's MCP surface: which tasks, in what order, with what inputs, would a user want inside a conversation? That mapping is the real integration work.
• Watch the named partners: how Adobe, Experian, Localiza, Peloton and Calm appear in Search and Gemini will show you what "good" looks like on this platform before you build.
• Do not rebuild around it yet. Until you are in the preview and can see real traffic numbers, treat this as a channel to test, not a strategy to bet the company on.

What we don't know yet

• Broader availability date: Google has said only "phases over the coming months" for the US preview. No date for general or international availability.
• Pricing and fees: not stated. Do not assume it is free, and do not assume a revenue share — neither has been announced.
• Ranking and surfacing rules: how Google decides which app appears for which query has not been explained.
• Data terms: what user data flows to your app, and under what terms, has not been stated.
• Real performance: traffic, conversion and retention for Connected Apps are Google's claims so far, not independently verified results.

None of that makes the platform unimportant. A developer platform inside the two most-used AI surfaces on earth is worth watching closely, and worth joining the waitlist for. But the honest status today is: preview, phased, waitlisted, review-gated, and commercially unproven. The door is open. Whether it leads anywhere profitable is something only the developers who walk through it will find out.

Source: Google, "New Connected Apps Platform launches for developers," by Chips Mistry and Mai Lowe, October 28, 2026.