Google Launches Connected Apps Platform Preview for Gemini and Search

Google launched the preview on October 28

Google announced the Connected Apps Platform on October 28, 2026, describing a unified way for developers to build an integration and submit it for the Gemini app, Google Search or both. Connected apps are meant to let signed-in users bring authorized account context into a conversation and complete actions in the developer’s service. This is an AI product and agent-distribution launch, not a new Gemini model or model API.

Availability is narrower than the launch headline. Google says access will open in phases and directs developers to apply for the preview. The reviewed pages do not identify eligible countries, acceptance criteria, review turnaround, quotas, uptime commitments, support tiers or a general-availability date. A public application form is an access route, not evidence that a particular developer can publish today.

One console manages two integration paths

For cross-platform services, Google documents a cloud-hosted remote MCP server as the recommended default. For Android apps, developers can expose native capabilities through AppFunctions using the Jetpack AppFunctions SDK, allowing execution to happen on the user’s device. Google presents the routes as complementary rather than equivalent: the remote path can serve Android, iOS and web users, while AppFunctions is tied to Android app capabilities.

Google Connected Console is the control plane described for registering tools, testing an app, choosing Search, Gemini or both, submitting for review and inspecting traffic, latency and error rates after launch. Google also says developers retain control over verified branding and authenticated accounts. AccessAllGPT did not enter the console, so the exact fields, review criteria, analytics definitions and operational controls remain unverified.

The build path has four documented phases

Google’s remote-server guide divides work into building the MCP server, validating it locally with MCP Inspector, deploying and testing through Gemini Developer mode, and registering it in Connected Console. The guide recommends structured instructions, explicit safety annotations, clear schemas and interface metadata. A connected app can be invoked with its name and may remain in context for relevant prompts in the session.

That workflow reduces integration ambiguity, but it does not establish that a submitted app will be accepted or that Gemini will select the intended tool reliably. Before applying, freeze the smallest supported tool set, define every read and write boundary, test malformed and ambiguous requests, and preserve an ordinary web or mobile route for users when the Google surface is unavailable or the app is not selected.

Authorization is part of the product contract

Google recommends OAuth 2.1 delegated authorization for remote MCP integrations and documents the authorization-code flow with PKCE. PKCE is mandatory for OAuth 2.1 in the guide, and authorization-server metadata discovery is required for automatic onboarding. Those requirements describe a connection mechanism; they do not decide which scopes are safe or whether a particular action needs fresh user confirmation.

Use narrow, action-specific scopes and separate read, draft and commit capabilities. Do not let a broad account link become standing approval for purchases, messages, bookings, deletions or other consequential writes. Require a user-visible summary immediately before a consequential action, bind approval to the exact target and parameters, retain an auditable receipt, and make revocation effective without waiting for a model conversation to end.

More than 50 apps does not mean uniform availability

Google says it has launched more than 50 Connected Apps across Search and Gemini. Its October 28 announcement names Adobe, Experian, Localiza and Peloton as live for Gemini users, says those integrations are coming to Search in the following weeks, and announces a Calm integration for both products. The post does not provide a complete country-by-country, account-by-account or action-by-action matrix.

Consumer availability also has account and surface conditions. Google’s help page says personal users must sign in, can manage connections in settings and should check Keep Activity; it separately directs work and school accounts to different guidance. It also says Connected Apps do not currently work inside Gemini in Google Messages. Teams should verify the actual account, region, plan, surface and supported actions rather than infer access from a partner logo.

Google has not published platform pricing

None of the five reviewed first-party surfaces publishes a Connected Apps Platform fee, revenue-share arrangement, per-call charge, developer quota or paid support schedule. The absence of a listed price does not establish that development, hosting, review, distribution or future platform use is free. Developers still bear their own server, authorization, observability, support and downstream API costs.

Do not write a business case around hypothetical distribution. Model a preview as a capped acquisition and task-completion experiment: eligible accounts, connection completion, successful authorized actions, user cancellation, tool-selection errors, latency, support incidents and full cost per accepted outcome. Keep vendor-provided traffic metrics separate from your service’s confirmed state changes.

What builders should do next

Apply if a narrow, reversible service action benefits from appearing inside Gemini or Search and your team can operate delegated authorization safely. Start with one read or low-consequence action, a minimal schema, deterministic validation, least privilege, explicit error states and a non-conversational fallback. Test remote MCP and Android AppFunctions separately if both are relevant; they have different execution and availability boundaries.

Wait if the business case requires guaranteed distribution, specific markets, a fixed review date, published quotas, service levels or stable platform pricing. Reject the channel for any workflow that cannot tolerate model-mediated selection or cannot put deterministic authorization and confirmation outside the model. A preview justifies a bounded integration trial; it does not justify making Google’s conversational surfaces the only route to a critical service.

Disclosures

AccessAllGPT received no Google account access, preview approval, credentials, credits, briefing, demo, traffic data, review, payment or compensation for this article. Google and the named partners did not sponsor, review or endorse it. AccessAllGPT did not test, score or rank Connected Apps Platform, Gemini, Search, MCP or AppFunctions. AccessAllGPT Research is operated by NeuralArc, is independent, and is not affiliated with Google, Adobe, Experian, Localiza, Peloton or Calm. Publication-wide relationships are listed on the disclosures page.