Android Studio Now Accepts Any AI Coding Agent: Google Sets 2027 Foldable Deadline

Google’s Android Dev Summit 2026 — the platform’s first dedicated developer conference since 2022 — delivered two announcements that will reshape how Android apps are built and distributed: Android Studio now accepts any AI coding agent through an open protocol standard, and the Google Play Store will formally evaluate foldable-app quality starting in 2027 with boosted visibility for developers who meet the bar. The two-day event at the Google Event Center at Bay View in Mountain View, California, is concluding today, with Day 2 sessions running through 4 PM PT, after a packed first day that also produced the commercial launch of XREAL AURA — the first pair of wired Android XR glasses to reach pre-order availability, at a launch price of $1,099. Android Dev Summit developer tools posts detail the full scope of the day’s announcements.

Google’s AI Agent Market Is Now Inside Android Studio

The single most structurally significant announcement from the summit’s first day is the stable release of Bring Your Own Agent (BYOA) in Android Studio Rabbit 2, confirmed by Adarsh Fernando, Google’s Group Product Manager, Android Developer Tools. BYOA now stable in Android Studio as of the summit’s first day, with Android Studio Rabbit 2 releasing alongside the announcement.

The feature allows developers to install any of more than 40 AI coding agents that comply with the Agent Client Protocol (ACP) directly into Android Studio and give them full access to the IDE’s native capabilities: project structure and build understanding, symbol resolution, Compose Preview rendering, the Emulator, Logcat, and profiling tools. Agents already confirmed as BYOA-compatible at stable launch include Anthropic’s Claude Agent, OpenAI Codex, Google’s own Antigravity, and a growing roster of open-source and enterprise agents.

The technical foundation is ACP, an open, JSON-RPC 2.0-based wire protocol originally published by Zed Industries in August 2025 and now governed by a consortium including Zed, JetBrains, GitHub, Google, and Cognition. Under the Agent Client Protocol open standard, an IDE launches a coding agent as a subprocess and exchanges protocol messages bidirectionally — each agent implements the protocol once and runs in any compliant editor, without requiring custom integration work per editor. The analogy that best illuminates the stakes is to the Language Server Protocol (LSP), which Microsoft introduced in 2016 to standardize how IDEs communicate with language intelligence tools. LSP ended a world of per-editor language integrations by making any compliant language server work everywhere; ACP is doing the same for AI coding agents.

In the official Android Dev Summit announcement, Fernando explained that developer demand for flexibility in choosing the agents and models best suited for their specific work drove the decision to build open agent support into Android Studio directly.

Google has also shipped official Android CLI plugins for both Claude Code (Anthropic) and Codex (OpenAI), giving those agents first-class access to Android’s command-line toolchain — including the ability to build, test, and debug on real physical devices via Android Device Streaming, render Compose Previews for visual validation without launching an emulator, and run performance profiling via Perfetto system traces. Google internal testing confirmed that agents using the android preview command completed UI tasks 77% faster while using up to three times fewer tokens compared with agents without it.

The Android Performance Analyzer received a separate update integrating with AI agents via Perfetto SQL, allowing agents to capture system traces from the command line or CI pipelines and propose targeted fixes autonomously.

Play Store Will Enforce Foldable Quality Starting in 2027

For app developers who have been treating Google’s adaptive-design guidelines as optional recommendations, the summit delivered a deadline. Google confirmed that starting in 2027, the Google Play Store will formally evaluate foldable app quality and award boosted visibility and prominent placement to apps that meet the bar, as AndroidGuys Android Dev Summit highlights confirm.

The specific quality requirements will be announced later this year, but the implication is clear: an app that fails to optimize for foldable form factors — which include the folded-phone posture, the fully unfolded tablet posture, and the tabletop posture used in flat-resting XR and foldable configurations — will face a structural discovery disadvantage on the world’s largest Android distribution platform.

This marks a shift from Google’s longstanding soft-guidelines approach. Since at least 2022, the company has published adaptive design documentation and recommended large-screen optimizations, but without tying those guidelines to distribution mechanics. Starting in 2027, the Play Store’s own algorithms will create a commercial incentive structure that soft guidelines could not.

To help developers meet the bar, Google updated the Compose adaptive skill — a new AI-powered capability that can audit a Compose UI and automatically implement keyboard shortcuts, custom pointer cursors, hover states, and tooltips; migrate navigation patterns; refactor layouts to Grid, Flexbox, and mediaQuery; manage end-to-end state; and convert media and camera screens into tabletop layouts suitable for foldable-posture use. The Compose adaptive skill for foldable design also helps apps scale to Googlebook, Google’s new laptop category, letting developers target both the phone and laptop form factor from a single codebase.

Android XR Developer Tools Reach Stable: Build Without Hardware

The Android XR track delivered news that directly determines whether commercial investment in XR app development is now rational: the Core Jetpack XR SDK libraries stable — Jetpack SceneCore, ARCore for Jetpack XR, and XR Runtime — meaning they now carry long-term API stability and backward compatibility guarantees.

Perhaps more practically consequential for the 2026 development window: XR emulators now stable in Android Studio, including emulators for display glasses, audio glasses, and XR glasses. The updated emulators allow developers to customize testing environments with their own 360-degree photos or a live camera feed from a connected camera, and to pair virtual phones with virtual XR glasses through an improved Pairing Wizard. Developers who have been waiting for hardware to build XR experiences no longer need to.

The Android XR Engine Hub is also now stable, providing dedicated workflows and performance trace access across the three major game and spatial engines — Unity, Godot, and Unreal. Geospatial APIs that allow developers to anchor digital content to specific real-world locations with spatial tracking have landed in both the ARCore for Jetpack XR SDK and Unity, as confirmed in the Android Dev Summit XR sessions.

A dedicated session in the XR track covered building audio-first experiences for intelligent eyewear with Gemini Nano 4, addressing app patterns designed primarily for voice and sound interaction rather than visual interfaces — a key design paradigm for lightweight smart glasses that carry no large display. See the Android Dev Summit session catalog for the full session lineup.

What Android 18 Has Already Shown Developers

One of the more noteworthy signals at the summit is what amounts to the first official public preview of Android 18 — surfaced not as a press release but as a conference session titled "Elevate your apps with the latest graphics features in Jetpack Compose and Android 18." The Android 18 graphics session at summit promises new graphics primitives including mesh gradients (where multiple colors blend from multiple points across a surface) and progressive blurs, along with guidance on implementing them without sacrificing battery life or frame rate.

For context: Android 17 reached stable on June 16, 2026. A preview of Android 18 graphics APIs in late October represents an unusually early look at the next major OS release and signals the development cycle is further along than many observers expected.

On the Compose side, Compose 1.13 has a confirmed stable release incoming, bringing Grid and Flexbox to stable and adding Progressive Blur and Formatted Text as framework-level capabilities. AppState, a new alpha API, brings Compose’s reactive model down to the architecture layer, enabling state preservation across configuration changes for both developers and AI agents working on the same codebase.

XREAL AURA Is the First Android XR Glasses on Pre-Order — Here’s the Price

Alongside the developer tooling announcements, Google and XREAL jointly announced the XREAL AURA on stage during Day 1 — the world’s first wired XR glasses powered by Android XR, co-developed with Qualcomm on the Snapdragon Reality Elite platform. Pre-orders opened October 28 at XREAL.com and, in the United States, at Best Buy, with launch pricing of $1,099 as confirmed by Digit.in Dev Summit coverage.

The glasses weigh under 95 grams (3.35 oz) and feature Sony micro-OLED displays running at 120 Hz with a 70-degree field of view, built-in Bose speakers, adjustable electrochromic dimming, and electrochromic (light-responsive) lenses. The compute hardware lives in a separate puck that clips to the user’s waistband, connected to the glasses by a wire — a split design that keeps the frame weight under 95 grams by offloading the Snapdragon processor, battery, and heat output into the puck. Regular pricing after the promotional window is $1,279 (12 GB RAM / 256 GB storage) or $1,499 (16 GB RAM / 512 GB storage). The launch promotion runs through December 2026.

XREAL AURA launches with 150 XR launch experiences confirmed and is available to pre-order in the US Canada Japan South Korea availability. Shipping is expected to begin in mid-November. Europe is not included in the initial launch window.

What Buyers Should Understand About XREAL’s Chinese Ownership

XREAL (Beijing Xreal Co., Ltd.) is headquartered in China, with global headquarters in Shanghai’s Pudong district. Investors include state-owned Pudong Venture Capital Group and Alibaba Group. This matters to buyers because Chinese companies are legally subject to China’s National Intelligence Law (2017), whose Article 7 requires that all organizations and citizens must support, assist, and cooperate with national intelligence work. The Data Security Law (2021) and Cybersecurity Law (2017) add government access provisions for data held by Chinese companies. These are not contested claims — they are the operative legal conditions under which any Chinese company operates, regardless of where its servers are located, where its products are sold, or what its privacy policy states.

For XREAL AURA specifically, the data categories the device collects include images from three onboard cameras, voice input processed by Gemini, and spatial tracking data including head position and hand movement. No independent security audit of XREAL AURA has been published as of this writing, which means there is currently no third-party confirmation or denial of data transmission practices beyond XREAL’s own disclosures. XREAL AURA is not on the Federal Communications Commission’s Covered List, the regulatory mechanism used to restrict Chinese hardware with confirmed national security concerns.

Buyers who want to limit their exposure can review Gemini permission settings in Android XR, restrict camera and microphone access to specific applications, and segment the device on a separate network. No available mitigation fully resolves the underlying legal obligation.

For the complete technical breakdown of XREAL AURA’s birdbath optical architecture, the split-compute engineering tradeoffs, and a fuller analysis of the Chinese data law framework, see the prior TechTimes coverage below.

Is Android XR Ready for Commercial Investment?

Taken together, the summit’s announcements describe a platform that has crossed a threshold. Before stable SDKs, stable emulators, and the XR Engine Hub, building for Android XR meant accepting the risk that APIs would change and that testing required physical hardware few developers had. Those barriers fell at the summit. XREAL AURA’s commercial launch — with 150 launch apps already confirmed and Godot Engine among them, as the Godot Engine XREAL AURA launch post confirms — provides the first concrete evidence that the developer ecosystem is building ahead of the consumer hardware curve rather than behind it.

Google’s four hardware partners for Android XR glasses — XREAL, Samsung, Warby Parker, and Gentle Monster — represent a platform model rather than a single product. Samsung’s smart glasses (internal codename "Jinju") and the fashion-brand collaborations have not yet reached commercial launch, which means XREAL AURA is the only Android XR glasses a developer can actually buy or test on today. That makes the emulator stability announcement even more significant: it is the practical bridge between platform and production for anyone not yet ready to order hardware at $1,099.

The 2027 Play Store foldable gate, meanwhile, converts five years of adaptive design guidance from recommendation to distribution mechanic. For mid-sized development teams weighing whether foldable optimization belongs in their 2025–2026 roadmap, that deadline provides a concrete financial argument: apps that do not meet the foldable bar will see less Play Store visibility when the gate opens. The specific requirements are still to be published later this year, giving developers a narrow planning window to scope the work before the criteria are fixed.

---

Frequently Asked Questions

Can I use Claude or ChatGPT instead of Gemini in Android Studio now?

Yes. Google’s BYOA (Bring Your Own Agent) feature, now stable in Android Studio Rabbit 2, allows developers to install any Agent Client Protocol-compatible coding agent directly inside the IDE. Anthropic’s Claude Agent and OpenAI’s Codex are both confirmed compatible at launch, along with Google’s own Antigravity and more than 40 other agents. Each agent gets the same native Android Studio access as Gemini — including Compose Preview, the Emulator, Logcat, and the full project structure. Google has also released official Android CLI plugins for both Claude Code and Codex.

Why does the BYOA open-agent model matter beyond convenience — what makes ACP significant?

The Agent Client Protocol (ACP) is doing for AI coding agents what the Language Server Protocol (LSP) did for language intelligence in 2016: converting a fragmented ecosystem of per-editor integrations into a single open standard. Before LSP, each code editor needed custom integrations for each programming language’s tooling. After LSP, any compliant language server worked everywhere. Before BYOA with ACP, each AI agent needed custom IDE plugins to work in Android Studio. After stable ACP support in Android Studio, any compliant agent implements the protocol once and works everywhere. The implication is that AI agent quality — not IDE integration effort — becomes the competitive differentiator.

What does Google’s 2027 Play Store foldable quality gate mean for my app?

Starting in 2027, Google Play will formally evaluate whether apps are optimized for foldable form factors and will give apps that meet the quality bar boosted visibility and prominent placement in search and discovery. Apps that do not meet the bar will not be removed from the store, but will see a discovery disadvantage. The specific technical requirements will be published later in 2026. Developers should use the Compose adaptive skill to audit their current UI and identify what changes would be needed before the gate opens.

What should I know before buying XREAL AURA, given that XREAL is a Chinese company?

XREAL is legally subject to China’s National Intelligence Law (2017), which requires Chinese organizations to cooperate with national intelligence requests regardless of their privacy policies or server locations. XREAL AURA collects camera imagery from three onboard cameras, voice data through Gemini, and spatial tracking data. No independent security audit of the device has been published. You can limit exposure by restricting camera and microphone permissions in Android XR settings and network-segmenting the device, but no mitigation fully removes the legal obligation. For a full breakdown of the legal framework and technical architecture, see TechTimes’ earlier XREAL AURA coverage.