Meta’s Wearables Device Access Toolkit, the bridge that lets third-party apps talk to its Ray-Ban Meta glasses, reached version 1.0 on Maven Central on September 24. Within days, an independent Expo module became the first community package to expose it to React Native developers.

The gap between 1.0 and a shippable app stays wide. A half-dozen capabilities in the release carry the experimental label. The list runs from camera audio streaming alongside video through standalone photo capture, voice invocations, and on-device speech transcription to motion and glasses inputs. Build on them and the changelog’s own wording applies: apps that rely on those features “cannot be published yet.”

The developer preview banner never came down either. The toolkit’s README still calls it a developer preview, and audio streaming and camera capture are both tagged as unavailable for production publishing. So the 1.0 tag delivers a version number, not a license to put an app in front of users.

One addition escapes the experimental label. Device state lets an app read battery level, charging state, don and hinge position, and thermal level from a paired set of glasses, enough to tell when they are put on, taken off, or folded shut. The same release adds a terminal error that stops older app builds that run against a newer SDK.

The npm registry was not new ground for the toolkit. Four earlier React Native wrappers predated the 1.0 tag, their last releases spread across January to July. The newest carries a disclaimer that it is community-maintained and unaffiliated with Meta.

Source: Mixed Reality News