Google’s latest developer toolbox – a quick overview
During the Android Dev Summit on 28 October 2026, Google unveiled a broad set of updates that aim to make Android app development faster, more intelligent and easier to scale across the ever‑growing range of Android devices. The announcements touch every part of the workflow – the IDE, the command‑line interface, AI‑driven coding assistants and even the emerging world of on‑device agents and extended‑reality (XR) hardware.
For UK developers, handset manufacturers and the contract‑deal market, the changes matter because they promise richer, more responsive apps that can run smoothly on everything from a budget Samsung phone to a high‑end foldable or a pair of XREAL glasses. Below we break down the most important pieces of the announcement and explain why they could affect the apps you see on the Play Store – and ultimately the value you get from your Android device.
1. Android Studio Rabbit 2 – the new home for AI coding agents
The most visible headline is the stable release of Android Studio Rabbit 2. While the name may sound whimsical, the upgrade brings a concrete capability: developers can now pick an AI “coding agent” from a catalogue of more than 40 ACP‑compliant agents directly inside the IDE. Options include Claude Agent, Codex, Antigravity and a host of other models that Google says are ready for production use.
"You now have more flexibility than ever before with updates to Android Studio and Android CLI to make it even easier for your agents to build high quality Android apps," the Android blog notes.
The integration works like a smart autocomplete on steroids – the chosen agent can suggest whole functions, refactor code, or even generate UI snippets in Jetpack Compose. For teams that already use GitHub Copilot or similar services, the ability to switch agents without leaving the IDE could shave hours off routine coding tasks.
What this means for UK developers
- Speedier prototyping – Smaller studios can iterate faster, a crucial advantage when competing for visibility on the Play Store.
- Cost control – By supporting a range of agents, teams can select free or lower‑cost models for routine work and reserve premium models for complex logic.
- Local compliance – The ACP (Android Compatibility Program) label assures that the agents meet Google’s security and privacy standards – an important consideration for GDPR‑compliant apps.
2. Android CLI – remote device streaming and instant Compose previews
The command‑line interface, long favoured by power users and CI pipelines, receives three major upgrades:
- Device streaming – Powered by Firebase, developers can now connect to a physical Android device over the internet, view the screen in real time and push builds without needing a USB cable. This is especially handy for testing on a range of UK‑specific handsets (e.g., the latest Samsung Galaxy S series or OnePlus Nord) from a remote office.
- Compose previews without an emulator – The CLI can render Jetpack Compose UI directly, eliminating the need to spin up an Android Emulator for visual checks. This cuts down on RAM usage and speeds up the feedback loop.
- Production‑grade profiling – Integrated Perfetto tracing now captures cold‑start latency, UI jank and background wake‑ups, mirroring the data Google Play analyses before an app upload.
Why contract‑deal seekers should care
Faster, more reliable testing means developers can ship bug‑free updates more often. For users, that translates into smoother performance on the devices they buy through carriers like EE, Vodafone or Three – a selling point when comparing contract offers.
3. New “agentic” APIs – letting on‑device AI talk to your app
Google is pushing the idea of agentic experiences, where an on‑device AI (or the system‑wide Gemini assistant) can invoke app functionality directly. Two key APIs were highlighted:
- AppFunctions (beta) – A unified “tool‑calling” layer that exposes app capabilities to agents. For example, a weather app could let Gemini fetch the current forecast without the user opening the app first.
- A2UI (alpha) – Short for Agent‑to‑UI, this lets an AI reply with a native Jetpack Compose UI instead of plain text. Imagine a chat with your banking app where the AI presents a clickable list of recent transactions, all rendered with your app’s own design language.
These APIs are part of the broader Android Intelligence System, which aims to blend prompted assistance (you ask the AI) with proactive assistance (the AI offers help based on context).
Impact on the UK market
- Better voice‑first experiences – With Google Assistant already popular on UK devices, tighter integration could make third‑party services feel more native.
- Competitive edge for local developers – Small UK studios that add agentic features may stand out in crowded categories like finance, travel or health.
- Potential for new revenue models – Apps could expose premium functions via AppFunctions, opening up micro‑transaction opportunities.
4. Adaptive Compose – one codebase for phones, tablets, laptops and foldables
Google’s push for Compose‑first development continues with a set of adaptive tools:
- AppState (alpha) – Brings Compose’s reactive model down to the state layer, helping apps preserve UI state across device rotations, foldable postures and even desktop windows.
- Navigation 3.1.2 – Now stable, adds richer deep‑link handling and predictive back gestures.
- Compose 1.13 (upcoming stable) – Will ship built‑in Grid and Flexbox layout support, progressive blur effects and formatted text handling.
- Adaptive skill for Compose – An AI‑driven assistant that audits your UI, adds keyboard shortcuts, pointer cursors, hover states and tooltips, and refactors layouts for foldable “table‑top” modes.
Why this matters for UK users
The UK market has a high adoption rate of premium foldables (e.g., Samsung Galaxy Z Fold) and an emerging interest in ChromeOS‑based laptops that run Android apps (Googlebook). Apps that automatically adapt to these form factors will feel more polished, reducing the friction that sometimes discourages users from trying new device categories.
5. XR SDK reaches stable status – building for glasses and AR headsets
In partnership with XREAL, Google announced the XREAL AURA – the first wired XR glasses that run a full Android stack. Alongside this hardware launch, the Jetpack XR SDK libraries have graduated to stable, providing:
- SceneCore, ARCore for Jetpack XR, and XR Runtime – Production‑ready APIs with long‑term stability guarantees.
- XR emulators in Android Studio – Developers can now design and test XR experiences without needing the physical glasses.
- XR Engine Hub – A unified workflow for Unity, Godot and Unreal, including performance tracing.
Relevance for UK developers and consumers
- Local content creators – UK game studios and media firms can experiment with immersive experiences for events, education and retail.
- Enterprise use‑cases – Logistics, manufacturing and healthcare sectors (which have strong UK footprints) can prototype AR overlays for training or maintenance.
- Future‑proofing – As XR glasses become more affordable, early adopters will have a richer ecosystem of apps, potentially driving new hardware sales through carrier bundles.
6. How the updates fit into the broader Android ecosystem
All of these announcements reinforce Google’s shift from viewing Android merely as an operating system to positioning it as an intelligence system. By exposing more AI‑driven hooks, simplifying cross‑form‑factor development and stabilising XR tooling, Google is laying the groundwork for a more seamless user experience across the entire Android device family.
For UK consumers, the downstream effect is likely to be:
- More responsive apps – Faster build cycles and better profiling translate into smoother performance on budget and flagship phones alike.
- Richer interactions – Agentic UI and adaptive layouts mean fewer “clunky” experiences when moving from a phone to a foldable or a laptop.
- New categories of apps – XR and on‑device AI open doors for innovative services that could become part of future contract bundles (e.g., AR‑enhanced navigation or AI‑assisted fitness coaching).
7. Getting started – what developers should do now
- Update Android Studio to the latest Rabbit 2 build and explore the AI Agent plugin marketplace.
- Try the CLI streaming feature on a test device via Firebase – the documentation includes step‑by‑step instructions.
- Experiment with AppFunctions in a sandbox project to see how an on‑device agent can call a simple function (e.g., toggle a setting).
- Run the Adaptive Compose skill on an existing Compose UI to automatically generate desktop‑ready layouts.
- Download the XR emulator and follow the quick‑start guide if you’re interested in AR/VR prototypes.
Google encourages feedback through the Android Developer Console, so early adopters can shape the final releases.
8. Bottom line for the UK Android community
The suite of tools announced at the Android Dev Summit is a clear signal that Google wants developers to move faster, think bigger and embed intelligence at the core of their apps. For UK developers, the combination of AI‑assisted coding, remote testing, adaptive UI and stable XR libraries could lower the barrier to creating high‑quality experiences that work across the full spectrum of Android hardware – from low‑cost smartphones to premium foldables and emerging glasses.
For consumers, the ripple effect will be more polished apps, fewer crashes, and new kinds of interaction that make the Android ecosystem feel more cohesive, regardless of the device you pick up on a contract deal.
Stay tuned to Android‑Mobiles.co.uk for deeper dives into how these tools translate into real‑world app performance and which UK‑focused apps start to leverage them first.
