--- title: "Android XR and on-device agents: what to keep on your side" url: "https://barbairians.com/blog/android-xr-what-you-can-keep-on-your-side" description: "Android XR turns glasses and phones into bodies for a platform agent. For an owner it is one more layer of dependency on big tech, and some of it can stay yours." --- # Android XR and on-device agents: what to keep on your side October 13, 2026·4 min read·BarbAIrianS Every few years big tech finds a new place to stand between a company and its own work. First it was the server room, then the office suite, then the CRM, the accounts and the ERP. Each time the offer was sensible and the price was fair. Each time the company ended up running on somebody else’s layer, at somebody else’s pace. The next layer is being built right now, and it is closer to the work than any of the others. It is the agent that lives on the devices your people wear and carry. ## What Android XR actually is Android XR is Google’s platform for XR devices: headsets, glasses with displays, and audio glasses without them. It is developed with Samsung and Qualcomm, and Gemini is its assistant layer. The first device was Samsung’s Galaxy XR headset in October 2025. At Google I/O in May 2026 Google showed smart glasses with Samsung and Qualcomm, with frames from Warby Parker and Gentle Monster among others. Samsung has announced its own Gemini glasses for November 2026, without a price or an exact date. And on 7 October 2026 XREAL Aura became the first priced Android XR device in the display-glasses class, from USD 1,279. The detail that matters for an owner is how Google describes the audio glasses. They work with a phone, Android or iPhone, and the Gemini agent carries out multi-step tasks on the phone in the background. The glasses are its voice and its camera. Read that again with your company in mind. The agent sees what your employee sees, hears what they hear, and acts on a phone that holds their email, calendar and company apps. That is not a gadget. It is a new operating layer, and like every layer before it, it has an owner. ## The dependency, layer by layer - **The body belongs to the device maker.** Glasses, puck or phone: hardware you buy, on a release cycle you do not set. - **The nervous system belongs to the platform.** Android XR decides how apps reach the camera, the display and the assistant. For glasses, Google’s SDK runs your app on a host device such as a phone and projects it to the glasses; that is a sensible design, and it is Google’s design. - **The voice belongs to the assistant.** Gemini is the default way a wearer asks for anything. Your software comes second, if it is invited at all. - **The split between pocket and cloud is not published.** Neither Google nor XREAL says publicly how much of the agent’s work happens on the device, on the phone or in the cloud. So nobody outside can tell you what leaves the building. - **The memory belongs to whoever runs the agent.** What was seen, heard, asked and done is a record of how your company works, collected at a level of detail no ERP ever reached. Analysts are already counting the arrival. Counterpoint, quoted by Android Authority, put shipments of AI glasses in the first half of 2026 at 263% up on a year earlier, with 96% of them glasses without a display. Most of that is the audio-glasses pattern: the glasses listen and look, the phone and the cloud do the thinking. ## What you can keep on your side The answer is not to refuse the devices. Your staff will wear them anyway, the way they brought smartphones to work before anyone had a policy. The answer is to decide which layers are yours. - **Your data.** Stock, orders, job sheets, customer history: they stay in systems you control, and any agent reads them through a door you built, with a key you can take back. This is the same line we drew in [data is the moat you cannot rent](https://barbairians.com/blog/data-is-the-moat-you-cannot-rent). - **Your agent’s remit.** What an agent may do in your systems, up to what value, and where it must ask a person. That belongs to you, not to the platform’s assistant. We set out the basics in [an agent is not a chatbot](https://barbairians.com/blog/an-agent-is-not-a-chatbot). - **Your record of actions.** Keep your own log of what any agent did in your systems, whatever the platform logs on its side. If the record of your operations lives only with the platform, so does the ability to learn from it. - **Your way out.** Write the workflow so the glasses, the assistant or the platform can be swapped. If replacing one device brand would mean rebuilding your process, you are not using a platform; it is using you. - **Your rules for recording.** What may be captured, how long it is kept, and what employees and visitors are told. EU rules on data and on AI already expect you to know; the point is to know before the first pair is worn, not after. The developer side is open enough to start. The Android XR SDK, with Jetpack Projected for glasses and an emulator, is public at [developer.android.com/xr](https://developer.android.com/xr). That means the parts that are yours — data access, remit, logs — can be built and tried on ordinary phones before any glasses ship to Europe, and they will keep working whichever glasses turn up. ## A check for this week List the three most sensitive things your staff look at during a working day: a customer file, a price list, a machine setting. For each, ask: if an assistant on their glasses saw it, where would that image go, who could act on it, and could you ask for it back? Wherever the honest answer is “we would not know”, that is the layer you have not yet decided to keep. What a single device gets right and what it hands to the platform is in [smart glasses are the new gate](https://barbairians.com/blog/smart-glasses-are-the-new-gate). What this podcast is about, and who it is for, is on the [home page](https://barbairians.com/). - Android XR - on-device agents - big tech - sovereignty ## Keep reading - [AI factories in Europe: who will own the tokens](https://barbairians.com/blog/ai-factories-in-europe-who-owns-the-tokens) - [The model contract: what not to sign with an AI vendor](https://barbairians.com/blog/the-model-contract-what-not-to-sign-with-an-ai-vendor)