Google Connected Apps Platform is entering developer preview, giving businesses a new way to bring their services into Gemini and Google Search. Announced on October 28, 2026, the platform lets developers connect applications through standardized interfaces and manage integrations from a central console.
The initiative could expand what Google’s AI products can accomplish beyond answering questions. Users may be able to access information from connected accounts and complete supported tasks directly within their conversations. Google is also expanding its collection of third-party integrations, including services from Adobe, Peloton, Experian and Calm.
Google Connected Apps Platform Unifies Gemini and Search Integrations
Until now, developers building services for conversational AI products have often faced different integration requirements across platforms. Google’s new system aims to simplify that process by providing a shared development and management environment.
According to Google’s official announcement, developers can build an integration and make it available through the Gemini app, Google Search, or both. The company describes this approach as a way to reach users across its products without creating separate integrations for every destination.
The platform is designed around authorized access to third-party applications. A user can connect an account and then interact with supported information or functions through an eligible Google product. This means an AI assistant could become an alternative interface for everyday services.
For example, a user might ask an assistant to retrieve information from a connected productivity service or perform an action using an authorized application. The exact capabilities depend on what each developer exposes and what Google supports.
The platform does not automatically provide access to every app or account. Developers must implement supported interfaces, and users must authorize connections where authentication is required.
How Model Context Protocol Connects Third-Party Services
Model Context Protocol, or MCP, is central to Google’s implementation. The open standard allows AI systems to communicate with external tools and data sources through a defined interface.
Instead of creating a custom connection for every AI assistant, developers can expose supported capabilities through an MCP server. An authorized client can then discover and use those functions according to the integration’s permissions.
Google supports cloud-hosted MCP servers as one development path. These remote connections suit services that operate through online accounts, cloud applications, and other server-based systems.
The company also provides an Android integration path. Its developer documentation explains how applications can expose native device functionality through Android MCP and the AppFunctions APIs.
This approach could be particularly useful for actions that should execute locally on a smartphone. Rather than routing every supported operation through a remote server, an Android application may provide selected functions directly to an intelligent assistant.
Google’s documentation also addresses authorization through OAuth 2.1 for applicable remote integrations. Authentication is important because connected services may involve personal information or actions performed on a user’s behalf.
Google Connected Console Handles Testing and Publishing
Developers will manage their integrations using Google Connected Console, a centralized interface for the new platform. The console covers registration, testing, review submission and publication.
After implementing the required connection, a developer can register the service and test its behavior. Before submitting it for review, the developer selects whether the integration should appear in Search, Gemini, or both products.
Google also provides operational information after an integration goes live. Developers can monitor traffic, response latency and error rates to understand how their services perform.
These measurements can help identify technical problems. For example, a rise in latency may indicate that an external service is responding too slowly. Error monitoring can also highlight failed requests that require investigation.
The console includes tools for managing how an application is represented. Google says developers can maintain verified logos and authenticated account connections, helping users distinguish legitimate integrations from unrelated services.
However, publication is not automatic. Connected Apps must pass Google’s applicable review process, and access to the developer preview is being introduced gradually.
Adobe, Peloton, Experian and Calm Join Google’s Ecosystem
Alongside the development platform, Google announced an expansion of its Connected Apps partnerships. The company says it has launched more than 50 integrations across Search and Gemini, covering areas such as productivity, event ticketing, health and fitness.
Integrations involving Adobe, Experian, Localiza and Peloton are already available to supported Gemini users. Google plans to extend those connections to Search in the coming weeks.
The company also announced an upcoming Calm integration for both Search and Gemini. Calm provides meditation, sleep and wellness content, making it another example of how conversational interfaces may connect with specialized consumer services.
The participating companies represent different types of applications. Adobe focuses on creative software, Experian provides financial information services, and Peloton offers connected fitness experiences. Localiza operates in the vehicle rental and mobility sector.
Google has not said that every function these companies offer will be accessible through Connected Apps. Availability and supported actions depend on each integration, user eligibility and the Google product being used.
The expansion nevertheless demonstrates Google’s broader objective. Rather than limiting Gemini to Google’s own applications, the company wants third-party services to provide useful functions within its AI experiences.
What Connected Apps Could Mean for Google Search
Google Search has traditionally helped users discover information and navigate to external websites. Connected Apps introduce another possibility: completing certain tasks through the search experience itself.
A connected service could allow users to act on information without manually moving through several separate interfaces. This may simplify some workflows, particularly when a request involves an existing account or a supported transaction.
For developers, the potential benefit is access to users who are already expressing a specific intention. Someone searching for a service may be ready to take the next step, making an integrated action more relevant than a general recommendation.
However, the development also raises questions about how businesses maintain relationships with their customers. If more interactions occur inside Google’s products, developers will need to consider branding, account ownership and the visibility of their services.
Google’s emphasis on verified identities and authenticated accounts addresses part of that challenge. It does not resolve every commercial question, including how connected applications might affect website visits or customer acquisition.
The company has not published evidence demonstrating that the platform increases conversions, revenue or engagement for participating developers. Those outcomes will require measurement as more integrations become available.
Privacy and Account Permissions Remain Important
Connected applications introduce privacy considerations because they can involve account information and actions performed through an AI interface. The risks depend on the data and capabilities each integration makes available.
Google says its platform is designed around authorized tools and account connections. Developers implementing remote MCP services are directed to OAuth-based authentication, which lets users authorize access without exposing their account passwords to every connected client.
Authorization alone does not guarantee that an integration is free from security risks. Developers still need to protect sensitive information, validate requests and limit the actions their services permit.
Users should also understand what an application can access before connecting it. The appropriate permissions for retrieving information may differ from those required to modify account settings or complete transactions.
The platform’s long-term usefulness will depend partly on whether Google and participating developers can make these permissions understandable and maintain reliable safeguards.
Developer Preview Availability and Future Expansion
The Google Connected Apps Platform is not yet a universally available development service. Google is opening access in phases and plans to add more developers, markets, and supported products over the coming months.
Interested developers can review the official documentation and apply to participate in the preview. The available materials explain the MCP integration path, Android App Functions, and the Connected Console publishing process.
Google has not announced a date for unrestricted public developer access. The company also has not confirmed when every existing Gemini integration will become available in Search.
These limitations are important for businesses evaluating the platform. A development preview offers an opportunity to experiment, but it does not guarantee immediate distribution to all Google users.
Why Google’s Connected Apps Strategy Matters
Google’s announcement reflects a broader change in how AI assistants interact with digital services. Instead of functioning only as conversational information tools, assistants are increasingly being designed to retrieve authorized account data and perform practical tasks.
The Connected Apps Platform establishes a common technical path for developers seeking to participate in that shift. Its combination of MCP, Android App Functions and a centralized console could reduce the effort required to maintain integrations across supported Google products.
Much will depend on the quality of individual connections. Reliable authentication, clear permissions and accurate execution will matter more than the number of services listed in the ecosystem.
For consumers, the most noticeable changes may arrive gradually as additional applications become available. For developers, the immediate opportunity is to test how their services could operate within Gemini and Search.
Google’s October 28 launch creates the foundation for those experiences, but the platform remains in preview. Its wider impact will become clearer as more developers gain access and real-world usage expands.
