Contents
What Google’s Connected Apps preview offers developers
Google announced the Connected Apps Platform preview on October 28, 2026. It gives developers a route to connect app capabilities with supported Google products, including Search and the Gemini app, subject to product support and configured availability. Google’s developer site continues to direct interested developers to apply for preview access; the public documentation does not establish an acceptance rate or review timeline.
Google’s launch announcement reported more than 50 Connected Apps across Search and Gemini and described phased partner rollouts. Those are dated company statements, not a guarantee that every named app is currently available on every Google surface. Check the relevant Google Help listing before making a current availability claim.
Choose between remote MCP and Android AppFunctions
Which integration path fits?
Google’s default for foundational cross-platform capabilities; reach depends on product support and configuration.
For local device context and close Android integration; documented for Gemini on Android.
This choice should be made before creating the connected app: Google says each app can select only one connection type, and the selection cannot later be changed for that app.
Choose the integration path before creating the app
| Decision factor | Remote MCP | Android MCP with AppFunctions |
|---|---|---|
| Best fit | Foundational capabilities intended for cross-platform reach | Capabilities requiring local device context or close Android app/system-UI integration |
| Documented scope | Supported Google products, subject to product support and configured availability | Gemini on Android |
| Important constraint | Choose this connection type when creating the connected app | Choose this connection type when creating the connected app |
Remote MCP is the documented default for foundational capabilities intended to reach users across supported Google products. Android MCP, implemented with AppFunctions, is for functionality that depends on local device context or closer integration with Android app and system-UI state; this path is for Gemini on Android. Neither route guarantees placement on every Google product or in every market.
How to apply and prepare an app for review
From setup to publication
- 1Choose category and connection
Select carefully: Google says neither choice can later be changed for that app.
- 2Complete app details
Add a description under 30 words, at least three capabilities, and at least three example prompts.
- 3Configure availability
Set supported regions, languages, and Google products; request only necessary user context.
- 4Test end to end
Check authentication, tools, confirmations, explicit app mentions, and natural-language prompts.
- 5Submit for review
Send the completed preview to Google for review and address any identified issues.
- 6Publish after approval
Approval makes the app ready to publish; publication remains a separate developer action.
Google’s Console workflow asks developers to choose an app category, define the app’s details and availability, configure testing, and submit the integration for review. The category establishes baseline capability requirements and cannot be changed after selection. Google’s documentation also calls for supported countries or regions, languages, and Google products to be specified.
Use this pre-submission checklist to catch choices and requirements that are easy to miss:
Pre-submission checklist
- 1
Check readiness
Confirm preview-access application requirements, account permissions, and technical prerequisites.
- 2
Make the fixed setup choices
Select the app category and connection type carefully; Google says neither choice can be changed later for that app.
- 3
Complete app information
Write an accurate public description under 30 words and provide at least three distinct, high-value capabilities and at least three example prompts.
- 4
Set availability and context
Configure supported countries or regions, languages, and Google products; request only the user context the integration needs.
- 5
Test the integration
Test authentication, tool execution, confirmation prompts, explicit app mentions, and natural-language prompts with configured testers.
- 6
Submit, then publish if approved
Submit for Google review. If approved, publish the app as a separate developer action.
The checklist reflects Google’s published setup guidance; completing it does not guarantee preview access or approval. The inspected documentation does not specify an approval timeline.
Describe capabilities accurately—don’t try to game app selection
Google distinguishes the public app description from instructions used to guide model behavior. The public description is a concise, user-facing summary of fewer than 30 words; Google says it is not used as model instructions. Capability entries should describe distinct, real tasks in clear terms.
For remote MCP, the developer guide separately recommends clear server instructions to help models recognize when to delegate tasks. Use each field for its documented purpose. Keyword-stuffing the public description, making overly broad claims, or describing capabilities the integration does not perform is not a supported routing strategy; Google’s policy prohibits deceptive descriptions intended to influence selection among Connected Apps.
Testing, review, and publication are separate steps
Before submission, test authentication and tool execution, including confirmation prompts where relevant. Google’s setup guidance also calls for testing with configured testers and checking both explicit app mentions and natural-language prompts. These checks help identify integration issues; they do not establish that Google will approve the app.
Google reviews and tests submitted integrations and may require remediation. Approval means the app is ready for the developer to publish; publication is a separate developer action, not an automatic result of approval.
Current availability and rollout caveats
At the time of the research check, Google’s Search Help page listed Instacart, Canva, YouTube Music, Yahoo Fantasy Football, and Sleeper Fantasy Football. Google cautions that availability varies by location, language, and device. A Search listing also does not mean every action is completed inside Google: in some cases, AI Mode hands the user off to the app to finish an action.
Treat the Search list as a snapshot of that help page, not a permanent or universal catalog. Google’s October 28, 2026 partner rollout statements should likewise be treated as dated announcements; verify each app and product surface before describing its present status.