Google Play Now Takes Apps for Audio Glasses, on the Phone Track, With Samsung's Pair Reportedly Due in Mid-December

Google Play Now Takes Apps for Audio Glasses, on the Phone Track, With Samsung's Pair Reportedly Due in Mid-December. Google has added augmented experiences on audio glasses to its ordinary mobile distribution path, while key Android XR libraries remain in alpha and Samsung's reported launch remains unconfirmed.

Google appears to have made this change through documentation rather than a separate announcement. When VR.org quoted Google's Android XR distribution page on September 28, it said Google Play distribution was "only available for immersive app experiences on XR headsets and wired XR glasses devices." Audio glasses were told to stay tuned, with no route to customers.

The same page now says distribution is available for immersive experiences "and for augmented experiences on audio glasses." Display glasses still carry the stay-tuned wording. Google's October 28 Android Dev Summit post, which moved several XR libraries to stable, does not mention the change. The distribution page footer dates its last edit to October 20, placing the wording change sometime in the three weeks after VR.org quoted the earlier version.

Gentle Monster's frame for Samsung-built audio glasses carries a camera, microphones and speakers but no display. Another pictured frame is from Warby Parker. Both images are identified as Samsung Newsroom material.

Existing phone APK, projected activity

Google has not created a dedicated store product or release track. Its guide says, "Play Console doesn't have a dedicated release track for audio glasses." Developers put glasses features in their existing phone APK on the mobile track, without specific publishing changes. Users download that app to a phone, which then connects to the glasses.

A headset runs a full APK on the device. Audio glasses instead run a projected activity: an Activity inside the phone app that the system pushes to the eyewear. Developers declare it with requiredDisplayCategory set to XR_PROJECTED. The XR_PROJECTED_LAUNCHER category lets Gemini find it when someone says "open" followed by the app's name.

Phone connectivity moved forward in the same period. Google's Play services release notes for v26.42, dated October 26, include this line under Device Connectivity: "[Phone] You can now connect Android XR glasses to your phone."

Compatible and Differentiated tiers

Google's Android XR quality guidelines divide apps into Compatible and Differentiated tiers. Compatible requires "zero additional developer effort" when an unmodified Android app does not rely on unsupported hardware. The platform carries standard notifications and Live Updates to glasses, reading them aloud on a pair with no display.

That means an Android app already on Play may send spoken notifications to glasses without its developers testing the experience or listening to the copy themselves.

Differentiated apps can receive a "Differentiated for Glasses" badge after implementing a projected activity. The route uses three libraries. ARCore for Jetpack XR reached 1.0.0 on October 21. Jetpack Projected is 1.0.0-alpha14, and Compose Glimmer is 1.0.0-alpha22; both releases are from October 21. Google's first-activity sample still opts in with @OptIn(ExperimentalProjectedApi::class).

Glimmer's latest release renamed three AlertDialog parameters. An audio-only app can skip Glimmer because a runtime check on CAPABILITY_VISUAL_UI shows whether visual UI is available. It cannot skip Projected. A badged Play listing can therefore depend on an API surface that remains free to change.

Android Wear offers an earlier comparison. Wear apps initially shipped inside the phone APK. In August 2017, Google said developers "should unbundle their Wear APK and upload it to the Play Store as a multi-APK," then removed the "Enhanced for Android Wear" badge from bundled apps beginning January 18, 2018.

The comparison has limits. A watch app could outgrow the phone, while a projected activity cannot. The earlier migration still shows why badge eligibility is a snapshot, not a promise.

Camera, recording and game restrictions

Google's policies for audio-only experiences apply to every app. Facial recognition, surveillance and doxxing are banned outright. The camera may support video calls and scene understanding, but not "real-time, one-to-many live streaming." Persistent background recording or transcription is prohibited when the wearer is not engaged in a user-initiated task.

Apps must not "change, dim, or disable" capture LEDs or interfere with thwart detection, which stops recording if the world-facing LED is covered. Games have an additional restriction: the tap gesture "must not be repurposed as a continuous controller for interactive games."

These rules arrive during wider scrutiny of camera glasses. California's capture-indicator bill died on the governor's desk on September 30. Senators Wyden and Markey gave Meta until November 25 to answer nine questions about its camera glasses.

Meta's glasses are already on shelves, but Meta still tells developers they will "soon be able to submit" toolkit apps for publishing. For now, Google has the open store while its compatible audio glasses are not yet available to buy.

Samsung's reported mid-December launch

ChosunBiz reported on October 30, citing electronics industry sources in an exclusive report, that Samsung fixed mid-December for first sales of its Intelligent Eyewear in South Korea and the US. Europe, China and Japan would miss the first wave, and the price remained under negotiation.

The report would replace a November date given by one unnamed official to The Korea Herald a month earlier. Samsung has confirmed neither date. On its earnings call, Samsung listed the "release of smart glasses" among its holiday plans, as 9to5Google reported. Google's consumer page still says "this fall," which mid-December is by about one week.

ChosunBiz says the first markets are South Korea and the US. It also reports that Galaxy XR followed the same pattern: Korea and the US first, followed by the UK nine months later. Speech-dependent features may therefore first reach Korean- and English-speaking users.

Testing can happen in the Android XR emulator. It became stable on October 28 and supports audio-glasses testing without physical hardware. Google warns that an unlaunched device may not appear in Play Console's device catalog "until closer to its launch," so excluding an app from a pair that has not shipped may not yet be possible.

For teams planning the next six months, existing notifications and Live Updates come first because they can reach glasses without app changes. Put any projected activity behind a removable flag while Jetpack Projected remains alpha. Give camera-policy requirements to whoever owns those features before scoping work.

Display-glasses development remains separate. Google still marks that path "stay tuned," the same wording audio glasses carried on September 28.