Google Connected Apps preview separates integration from Search and Gemini distribution

Google [announced a preview of its Connected Apps Platform on October 28](https://blog.google/innovation‑and‑ai/technology/developers‑tools/connected‑apps‑one‑place/), giving developers one place to build and manage integrations intended for Search, the Gemini app or both. The announcement separates a shared development route from the places where an app ultimately appears. Connected Apps themselves are not new that day. Google’s [July 16 Search announcement](https://blog.google/products‑and‑platforms/products/search/connected‑apps/) already described consumer integrations in AI Mode. The October development is the platform preview and a further set of partner integrations, rather than the first time users could connect an app to Google’s AI products.

The platform announcement describes two integration routes: a cloud‑hosted MCP server, or Android MCP using the AppFunctions APIs. Developers then use the Google Connected Console to register, test and submit the app. Before review, they choose Search, the Gemini app or both as its intended destinations.

An integration therefore needs more than a working connection to reach users through this platform. The announced route includes testing and a review submission, with a distribution choice made before that review. Google’s “build once” description should not be read as automatic publication everywhere.

The announcement does not provide a complete implementation or review contract. Exact protocol requirements, approval criteria and the timing for an individual submission are outside the verified announcement‑level details here. OpenTools has not registered or tested an app in the console.

Google says platform access is opening in phases, with more developers, markets and Google products to be added over the coming months. That establishes a phased preview, rather than unrestricted general availability or an identical signup experience in every country.

Partner distribution has its own timing. Google says integrations with Adobe, Experian, Localiza and Peloton are live in Gemini, while their arrival in Search is planned for the coming weeks. It also describes a forthcoming Calm integration across both Search and Gemini. Calm should not be counted as already live on the strength of this announcement.

For a developer planning a release, platform admission, the selected distribution surface and the user‑facing partner rollout are related questions, but they are not the same event. An app appearing in Gemini does not establish that the same integration has already appeared in Search.

Google [says developers can track traffic, latency and error rates once an app is live](https://blog.google/innovation‑and‑ai/technology/developers‑tools/connected‑apps‑one‑place/), alongside brand identity features such as verified logos and authenticated accounts. These are described management capabilities, not reported results for a particular integration. The immediate decision is which supported route and destination fit the app’s job, followed by the announced console and review process. The platform creates a prospective distribution route; the announcement does not show that using it will increase an app’s traffic, conversions or reliability. AI‑generated editorial illustration by OpenTools Team, based on [Google’s October 28 Connected Apps Platform announcement](https://blog.google/innovation‑and‑ai/technology/developers‑tools/connected‑apps‑one‑place/). Google says developers choose Search, the Gemini app or both before review; platform access is opening in phases. The pictured app waiting with two destinations selected is a conceptual metaphor, not Google Console UI, a technical architecture diagram or evidence of an actual submission, approval or distribution.