Expo Brings Meta Wearables DAT 1.0 to React Native

Mixed-News (Chris Steven, October 4, 2026) reports that an independent Expo module published on October 3 at 18:35 UTC became the first third-party package to WRAP and BRIDGE version 1.0 of Meta’s Wearables Device Access Toolkit for REACT NATIVE. The package EXPOSES the experimental capabilities Meta SHIPPED in that release — and Meta’s own changelog says apps built on those capabilities “cannot be published YET.”

Ray-Ban Meta smart glasses on display at Bild Expo 2025
Ray-Ban Meta is the one frame the Expo wrapper lists as verified hardware. Image: Wikimedia Commons (Tzim78 / CC BY 4.0).

The package is @chrisgocode/expo-meta-wearables-dat 2.2.0. Its changelog entry reads, in full, “upgrade to DAT 1.0 and expose experimental capabilities.” The README carries a clear DISCLAIMER: the project “is not affiliated with, endorsed by, or sponsored by Meta Platforms, Inc.” and calls itself “an independent, community-maintained WRAPPER around Meta’s public SDK.” Four other React Native wrappers for the same toolkit sit on npm, last published between January and July — all of them before 1.0 existed. The npm listing shows 2.2.0 updated October 3, 2026, confirming the UPGRADE to DAT 1.0.

Six Capabilities Meta Will Not Let You Release

Meta’s toolkit reached 1.0.0 on Maven Central at 17:40 UTC on September 24, after a RUN of 0.7.0 to 0.9.0 builds. Mixed-News notes six capability areas in that release marked EXPERIMENTAL: glasses INPUTS, MOTION, on-device speech TRANSCRIPTION, voice INVOCATIONS, standalone photo CAPTURE, and camera audio STREAMING alongside video. Those six are the ones developers can BUILD and TEST — but not RELEASE or SHIP to stores.

Meta Ray-Ban Display glasses front view with in-lens HUD
Ray-Ban Display is among the frames DAT targets; the Expo README marks display support wrapped but untested on hardware. Image: Meta / prior Metaverse Watcher upload.

Meta’s rule sits above the whole list. The experimental features “can be built and tested against, though apps using them cannot be published yet,” the Android changelog says. The project README still reads that the Wearables Device Access Toolkit is in developer PREVIEW, with audio streaming and camera capture both marked “unavailable for production PUBLISHING.” A 1.0 version number is not a shipping LICENCE here — the door stays CLOSED for store builds that lean on those flags, and Meta has not named a DATE when that changes.

The one addition not marked experimental is device STATE. An app can read batteryLevel, chargingState, donState, hingeState, and thermalLevel from a paired device — meaning it can be told when the glasses are put ON, taken OFF, or folded SHUT. That path is the only production-ready SIGNAL in the new surface — everything else stays behind the experimental GATE.

What the Wrapper Actually Verifies

The README is frank about hardware coverage. Ray-Ban Meta is listed as VERIFIED. Ray-Ban Meta Optics, Oakley Meta HSTN and Vanguard, and Meta Glasses are all listed as UNTESTED, and Meta Ray-Ban Display appears as “display capability wrapped; untested on hardware.” Background streaming is a stated non-GOAL because “the SDK doesn’t support it.” Developers who NEED production camera or audio paths still WAIT.

Ray-Ban Meta Gen 1 smart glasses with charging case
Device-state reads — battery, don, hinge, thermal — are the non-experimental path DAT 1.0 already exposes. Image: Wikimedia Commons.

Running it needs React Native 0.76 or newer, Expo SDK 52, iOS 17.2, Android API 31, and Xcode 16, and it will not run inside Expo GO. The package moved to its current name on September 4 with DAT 0.9, which is when the iOS floor ROSE from 16.0 to 17.2 and display support ARRIVED.

Ray-Ban Meta Gen 2 Wayfarer smart glasses with Polaroid lenses
Gen 2 Wayfarer frames remain the consumer face of Meta’s glasses stack while DAT tooling races ahead of store publishing rules. Image: Wikimedia Commons.

The same release adds an error that can stop an app DEAD. Meta describes DeviceSessionError.INSUFFICIENT_SDK_VERSION as “a terminal error indicating that developers must release a newer version of their app built with the current SDK,” so a glasses app that falls behind the toolkit STOPS working rather than DEGRADING. The toolkit is split across seven artifacts on Maven Central under the com.meta.wearable group — core, camera, display, inputs, motion, speech, and mockdevice — so a lagging client is a HARD break, not a soft warning.

Meta is publishing glasses development tools FASTER than it is opening the door behind them. Its Ray-Ban Display web toolkit added voice control for web apps on October 3, and its Immersive Web SDK reached 1.0 in September — both already covered here. A mock device module ships with the native toolkit so developers can BUILD without owning a pair, which is just as well: the capabilities this Expo wrapper just exposed are the ones Meta still will not let you SHIP.

Sources: Mixed-News; npm @chrisgocode/expo-meta-wearables-dat 2.2.0; GitHub wrapper README.

1 thought on “Expo Brings Meta Wearables DAT 1.0 to React Native”

Leave a Comment