Meta’s Wearables Device Access Toolkit hits a STABLE 1.0 TODAY. After a year in developer preview, the company says the toolkit — and the broader AI-glasses developer UPDATES tied to Connect — begins ROLLING OUT on SEPTEMBER 30, 2026.
The pitch is PRACTICAL rather than metaverse-grand: keep your existing iOS or Android APP, its BACKEND, and its store listing. The glasses become a hands-free FRONT END — camera, microphone, motion, and, on Ray-Ban Display, the right-eye HUD — while the phone still runs the LOGIC.
What 1.0 Actually Unlocks
According to Meta’s Connect AI-glasses developer recap, version 1.0 is the “STABLE, supported release to build on.” Users can launch experiences with “Hey Meta” voice INVOCATION, speak naturally while automatic speech recognition turns words into COMMANDS, and steer with a subtle SWIPE on Meta Neural Band. One INTEGRATION is meant to cover both display and displayless AI GLASSES.
Context is the other half of the release. Meta highlights high-quality CAMERA capture, voice inputs that become app actions, and MOTION streaming so an experience can RESPOND to head movement and orientation. The BirdSpotter SAMPLE — shown in Meta’s Connect session — composes motion, camera, speech, and display in one WORKING project, a faster read than reference DOCS alone.
Hardware support spans Ray-Ban Meta Gen 1 and Gen 2, Ray-Ban Meta Display, Oakley Meta HSTN, and Oakley Meta Vanguard, with capability DIFFERENCES by DEVICE. Meta’s version-dependency tables for SDK 1.0.0 call for Meta AI app BUILD V290 and glasses firmware V128 on those lines.
Stable SDK, Incomplete Storefront
STABILITY is not the same as DISTRIBUTION. Meta’s FAQ still promises developers will “soon” be able to submit toolkit and web-app experiences, with “more to share on submission and publishing TIMING soon.” VR.org, writing SEPTEMBER 28, framed that gap sharply: Meta has glasses on shelves and a 1.0 toolkit number, but not yet an open public DOOR for third-party publishing.
iOS adds a second LOCK Meta does not fully control. On the toolkit’s GitHub forum, Meta support confirmed that DAT 1.0 “doesn’t change this yet” for Made for iPhone (MFi) Product Plan authorization and PPIDs — Apple’s accessory paperwork for apps that declare com.meta.ar.wearable. TestFlight and release CHANNELS still work for testers; App Store DISTRIBUTION for third-party accessory talk remains gated.
The only firm near-term HARDWARE date on that calendar belongs to Ray-Ban Display reaching stores in France, Italy, and Germany on OCTOBER 13, per Meta as reported by VR.org — glasses U.S. buyers have already had for a year, now getting a wider European SHELF.
Why the Timing Matters
For mobile teams, SEPTEMBER 30 is less a consumer launch than a BUILD window. The toolkit is no longer preview-LABELED; the sample stack is PUBLIC; the remaining UNKNOWNS are storefront submission and Apple’s accessory rules. That is a different PROBLEM from Snap Specs or Android XR GLASSES, where publishing plumbing and shipping hardware are out of PHASE the other way.
Metaverse Watcher will watch whether Meta’s “soon” on publishing lands before European Display shelves FILL — and whether MFi paperwork moves with the STABLE SDK, or stays the BOTTLENECK that no amount of API polish SHORTENS.
Sources: Meta for Developers — Connect AI glasses recap; Meta Wearables DAT version dependencies; VR.org — Fall glasses platforms / SDK status (Sep 28); Digital Pulse Brief — Connect Day 2 developer announcements.