What happened
On October 28, 2026, Google announced XREAL AURA, developed with XREAL and described as the first wired XR glasses powered by Android XR. Google presents the product as a way to work, watch and play using a private spatial display while remaining able to see the physical environment. Its transparent lenses overlay digital content on the wearer’s field of view rather than enclosing it in an opaque headset. Google says the field of view is 70 degrees and the glasses weigh less than 95 grams.
The glasses connect by cable to a portable compute puck. Google says that puck contains the battery and Qualcomm Technologies’ Snapdragon Reality Elite platform, which debuts on AURA. The announcement frames the split between glasses and puck as a way to keep the eyewear light while handling processing externally. It does not provide battery-life figures, performance benchmarks or a detailed account of what workloads the platform can sustain.
Android XR brings Gemini and Google Play apps to the device. Google says the Play catalog includes more than 150 apps made for XR. Users can open multiple apps at once and arrange windows around them at different sizes. A Bluetooth keyboard and mouse can be paired, and the puck can be used as a trackpad. Google also describes Wired Mirroring: connect a laptop over a USB-C cable that supports video output, and its screen appears as a resizable window alongside Android XR apps. Google says this requires no software installation and that the display is visible only to the wearer.
Gemini can work across what is in view, including the laptop window, and can respond to requests about apps or the surroundings. Google says users can share their view and have Gemini highlight what to focus on, either in the room or on a screen. The announcement describes this as a new capability available from launch, but gives no technical detail about sensing, data handling, permissions or whether the feature works identically across all supported apps.
Orders opened on October 28 in the United States, Canada and South Korea through XREAL’s site, and in the United States also through BestBuy.com, according to Google. Orders were scheduled to open in Japan on November 2. Google says launch pricing starts at USD 1,099 through the end of the year, with shipments beginning in mid-November. The announcement does not state wider regional availability or a full set of hardware configurations. It also does not specify developer tooling, distribution requirements, or whether the 150-plus XR apps are all available in every launch market.
What the archive adds
A previous Field Note covered Meta’s effort to position a 100-gram VR headset as an everyday computing surface (Introducing Meta VR Glasses: A Cinema, Courtside Seat, and Workspace in Just 100 Grams). That was a related device-positioning story, not coverage of AURA. This is a new product announcement and a new fact in the broader push to make wearable displays usable for everyday work; its distinctive elements here are transparent lenses, a wired compute puck and Android XR with Gemini.
Trend signal
AURA offers a limited example of software interfaces being assembled around a user’s immediate task and context: multiple windows can be arranged in view, and Gemini can respond across screens and surroundings. That is consistent with the direction described in Model answers become task interfaces, but the announcement does not show a bounded, dynamically generated interface. The connection is suggestive, not proof that this pattern is becoming a shipped developer capability.
Why now
The timing is defined by the announcement itself: orders opened in three markets on October 28, with Japan scheduled to follow on November 2. That makes this more than a concept reveal, but the source does not explain why these markets were chosen or give a longer rollout plan.
Why it matters
For teams building AI products, AURA makes the interface and operating context part of the product question. Gemini is presented not only as a chat assistant but as help available across apps, a laptop window and the physical environment. If users can ask about what they see without switching to a separate screen, builders may need to think about how their software is represented, understood and controlled in spatial interfaces.
The announcement also shows that this experience depends on a system rather than a model alone: glasses, a cable-connected compute puck, Android XR, apps and an assistant are brought together. That is relevant to product architecture, but it is not yet a recipe for third-party teams. Google’s post does not say how developers can expose app context to Gemini, what permissions govern that access, or whether outside developers can create comparable XR experiences. Teams should therefore treat AURA as a platform signal, not evidence that their existing applications will automatically gain a wearable interface or assistant integration.
Limits and uncertainty
This is Google’s product announcement, so it establishes what the company says the device does, not independent measurements of comfort, display quality, latency, battery life or reliability. The source gives a launch price and a mid-November shipping start, but no sales figures or user testing. It does not explain privacy controls for Gemini’s access to a wearer’s view, how visual information is processed or retained, or what safeguards apply in public settings. Nor does it document third-party developer access, APIs, app submission rules or compatibility beyond the described Android XR and laptop mirroring features. Those omissions prevent conclusions about adoption, developer opportunity or the practical limits of contextual assistance.
Reader takeaway
AURA is a launched, wired Android XR device that pairs transparent glasses with a portable compute puck and Gemini across apps and the wearer’s view. The announcement makes a credible platform-level claim about spatial, context-aware computing, but leaves the developer interface, privacy model and real-world performance unanswered. For builders, watch what access and controls Google exposes next.
Open question
What permissions and developer interfaces will govern how Gemini and third-party apps use the wearer’s view?