Toggle search
Toggle menu
5.5K
6.1K
231
53.7K
VR & AR Wiki
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Meta Wearables Device Access Toolkit

vrarwiki.com · VR & AR Wiki
More actions
Meta Wearables Device Access Toolkit
Information
Type Software development kit
Industry Smart glasses, wearable technology
Developer Meta Platforms
Written In Kotlin (Android); Swift (iOS)
Operating System iOS 17.2 or later; Android 10 or later
License Meta Wearables Developer Terms, including the Acceptable Use Policy
Supported Devices Ray-Ban Meta (Gen 1) and Gen 2, Ray-Ban Meta Optics, Meta Glasses, Meta Ray-Ban Display, Oakley Meta HSTN, Oakley Meta Vanguard
Release Date September 18, 2025 (announced); December 4, 2025 (developer preview); September 24, 2026 (1.0.0)
Website https://wearables.developer.meta.com/


The Meta Wearables Device Access Toolkit (also called the Wearables Device Access Toolkit, the Device Access Toolkit or DAT) is a software development kit from Meta Platforms that lets third-party iOS and Android apps use the camera, microphones and speakers of Meta's camera-equipped smart glasses, which Meta calls AI glasses, and the display of the Meta Ray-Ban Display.[1][2] The apps run on the user's phone, not on the glasses: they receive video, photos and audio from the glasses and send audio or display content back.[3][1]

Meta announced the toolkit at Meta Connect on September 18, 2025, opened a public developer preview on December 4, 2025, and on May 14, 2026 began rolling out developer-preview access to the Meta Ray-Ban Display's screen.[4][5][6] It announced version 1.0, "a stable, supported release", at Meta Connect 2026; the latest version as of November 2026 is 1.0.1.[7][8] Publishing to the general public is still restricted: Meta's FAQ says developers will "soon" be able to submit experiences, and the changelogs state that apps using features labeled experimental "cannot be published yet".[9][8]

The initial developer preview did not include access to Meta's assistant, Meta AI; apps instead add AI features by sending camera images and audio to models of the developer's choosing, run locally or on cloud or edge platforms.[4][10][9]

Reviewed 2 November 2026. Every claim rechecked against Meta's current Wearables developer docs (21 pages), Developer Terms, Acceptable Use Policy, FAQ and Explore page, four Meta developer blog posts, the iOS and Android changelogs, READMEs, LICENSE and BirdSpotter README, Maven and GitHub version data, Road to VR and three UploadVR articles About review dates.

History

Announcement and preview

At the announcement, Meta said that publishing would be available only to limited audiences during the preview, and Road to VR reported that only select partners would be able to bring their integrations to the public.[4][3] Meta planned to open publishing to general availability in 2026 and said that Meta AI capabilities, including voice commands, were not part of the initial preview but "a key area we're exploring for future updates".[4] According to UploadVR, a handful of developers, including Twitch, Microsoft, Logitech's Streamlabs and Disney, had received an early version several months before, and the SDK would not at first send imagery to the Meta Ray-Ban Display or read gestures from the Meta Neural Band.[10]

When the public preview opened on December 4, 2025, UploadVR reported that developers could build the SDK into their phone apps and test it on their own glasses, "but they cannot yet ship it for general public use". It gave the stream maximum as 720p at 30 frames per second, "a limitation related to the use of Bluetooth", and said that the Ray-Ban Meta and Oakley Meta HSTN were supported, with Oakley Meta Vanguard and Meta Ray-Ban Display support to follow.[5] Version 0.4.0 added Meta Ray-Ban Display support in February 2026, at first without access to its screen: until May 2026 the only output that apps could send to Meta's glasses was audio over Bluetooth.[8][11] Meta's version-dependency tables first list the Oakley Meta Vanguard with the same release; Ray-Ban Meta Optics support followed in version 0.6.0 and Meta Glasses support in 0.8.0.[8][12] In April 2026 Meta wrote that publishing was "currently limited to select partners" and that it was working on voice invocation and Wi-Fi Direct.[13] On May 14, 2026, Meta began rolling out access to the Meta Ray-Ban Display's screen through two paths, both in developer preview: display components in the toolkit for existing iOS and Android apps, and standalone web apps written in HTML, CSS and JavaScript.[6]

Version 1.0

Meta's developer recap of Meta Connect 2026, published on September 24, 2026, said that "after a year in developer preview, Wearables Device Access Toolkit 1.0 is officially here", with the updates rolling out from September 30, 2026.[7] Version 1.0.0 added experimental input, motion, on-glasses speech recognition, voice invocation, standalone photo and camera audio features, along with device state readings and support for the Muse Code coding agent.[8][14][7] Integration versions created in the Developer Center before 1.0 do not work with builds that use the 1.0 SDK.[15]

Version history

Selected releases, with the dates given in the changelogs:[8][14]

Version Date Selected changes
0.1.0 October 30, 2025 First version for iOS and Android
0.2.0 November 18, 2025 SDK split into separate components; configurable stream frame rate of 30, 24, 15, 7 or 2 fps (Android)
0.2.1 December 4, 2025 Released on the day the public preview opened
0.4.0 February 3, 2026 Meta Ray-Ban Display support; first version whose version-dependency table lists the Oakley Meta Vanguard[12]
0.5.0 March 11, 2026 Fix allowing high-resolution (720x1280) video to be requested; on iOS, compressed HEVC streaming that continues in the background, app attestation and configuration files for AI coding agents
0.6.0 April 15, 2026 Ray-Ban Meta Optics support; session-based device management; phone camera as a mock camera feed
0.7.0 May 14, 2026 Display capability for Meta Ray-Ban Display; opt-in Device Access Toolkit App Model, required for the display capability
0.8.0 June 25, 2026 Meta Glasses support; on iOS, a unified error model and Wi-Fi transport
0.9.0 August 3, 2026 Consolidated camera capability; minimum iOS version raised from 15.2 to 17.2; App Model always enabled
1.0.0 September 24, 2026 Experimental inputs, motion, speech, voice invocations, photo capture and camera audio; device state; Muse Code support
1.0.1 October 9, 2026 Android fixes for HEVC buffer corruption and stream performance; no developer-facing changes on iOS

Architecture

Users register an app once through the Meta AI app, which then lists it under App Connections. The first time an app needs the camera it requests permission, and the user picks allow always, allow once or deny in the Meta AI app; microphone access uses the Bluetooth Hands-Free Profile and the phone's own permission dialogs.[1][16] Only one session can run on a pair of glasses at a time, and the wearer can pause, resume or stop it by tapping the glasses, closing the hinges or, with wear detection on, taking them off.[1] The documentation states that "Meta does not access photos/videos or audio that is transferred directly from the glasses to the third-party mobile app."[1]

Road to VR suggested that the likely reason for running apps on the phone is the glasses' strict limits on compute, thermals and battery life.[3] For the display, the SDK serializes the app's layouts, sends them to the glasses over Bluetooth and returns the user's interactions to the phone app as events; the glasses keep no application state.[2] The iOS SDK is distributed as a Swift Package and the Android SDK through Maven Central.[17][18]

Features

Camera

An app adds a camera stream to a session and picks a frame rate of 2, 7, 15, 24 or 30 frames per second and one of three portrait resolutions: 720x1280, 504x896 or 360x640 pixels. Both are constrained by the Bluetooth Classic link between phone and glasses. When bandwidth runs short, the stream first drops one resolution step and then lowers the frame rate, but never below 15 fps, and per-frame compression can make images look worse than their nominal resolution.[19] The glasses crop each frame to 9:16, correct lens distortion, stabilize the image and compress it with HEVC (H.265); the SDK decodes it to YUV frames by default or can hand over the HEVC frames. The SDK does not report camera intrinsics, so Meta tells developers to calibrate on stream frames, and it warns that stabilization makes visual-inertial tracking lose accuracy during head movement.[20]

Apps can capture a single frame during a stream.[1] A separate standalone photo mode, in beta, takes JPEG or HEIC images at up to the sensor's native 4032x3024 pixels. Stream frames cover a narrower field of view than these photos, the two modes cannot use the camera at the same time, and apps that use standalone photos cannot be published yet.[21][20]

Audio

Audio travels over the phone's Bluetooth connection. The A2DP profile carries output only, in stereo at 44.1 or 48 kHz; the Hands-Free Profile (HFP) carries two-way mono voice at 16 or 8 kHz and uses beamforming to isolate the wearer's voice. The profiles are mutually exclusive: activating HFP switches the glasses away from A2DP, and audio output drops to mono voice quality for the rest of the session.[22] A beta option, limited to development and beta release channels, instead delivers microphone audio inside a camera stream without switching to HFP, so output stays on A2DP. This audio arrives as uncompressed 16-bit PCM at 16,000, 44,100 or 48,000 Hz without beamforming; the documentation lists 16 kHz for speech, "including passing audio to a transcription service".[22]

Display

On Meta Ray-Ban Display, apps written in Swift or Kotlin can show layouts built from Meta's components (FlexBox containers, text, images, buttons and icons) on the glasses' heads-up display and play MP4 video.[2][6] The wearer operates them with the glasses' touchpad and the Meta Neural Band. Meta gives the display resolution as 600x600 and asks for videos under 400 pixels per side and 70,000 pixels in total. Each update replaces the whole display, since there is no partial update; the system may interrupt a session for calls or notifications; and the Device Access Toolkit has to be installed on the glasses through the Meta AI app in developer mode.[2] UploadVR described the path as letting "the HUD be used as a highly managed and controlled external display with button navigation and input, but the core of the app continues to run on the user's smartphone".[11] Web apps that run directly on Meta Ray-Ban Display are a separate path that needs no native app or SDK. Meta says one toolkit integration covers both display and displayless glasses.[9]

Inputs, motion and speech

Three beta capabilities from version 1.0.0 are available only in development and beta release channels.[23][24][25] Inputs delivers decoded events from the glasses and the Neural Band (directional navigation, select, back, the capture and action buttons, and drags) rather than raw sensor signals; real glasses do not yet deliver the back event.[23] Motion streams IMU samples from the wearer's glasses and needs no user permission. Each sample carries accelerometer, gyroscope, magnetometer and fused orientation readings, any of which can be missing, and names the sensor package that produced it: the glasses, the Neural Band or an unknown device.[24] Speech runs automatic speech recognition on the glasses and returns partial and final transcriptions with a confidence value. It requires the microphone permission, and Meta says not to depend on it in a production build.[25]

Voice invocations and device state

With voice invocations, labeled experimental in 1.0.0, the wearer says "Hey Meta, start" followed by the app's name, and Meta AI launches or foregrounds the app and passes it the request. The app name set in the Developer Center is the keyword that the voice service matches, and a WebMCP web app open in the foreground on the glasses takes priority.[26][8] Device state reports the battery level, charging state, whether the glasses are worn, whether the hinges are closed and one of eight thermal levels; it needs no permission and is available before a session starts.[27]

Testing tools and samples

Mock Device Kit simulates glasses, including camera streaming, photo capture, permissions and device state, so that integrations can be tested without hardware. A phone camera or a video file can stand in for the glasses camera, and up to three mock devices can be paired.[28] Since 1.0.0 it can also preview Meta Ray-Ban Display content on the phone, although the FAQ still says the kit "currently doesn't support display glasses".[8][9] Meta's sample apps include CameraAccess and DisplayAccess.[28][2] Its Connect 2026 recap said that a third sample, BirdSpotter, "composes motion, camera, speech and display in one working project"; the sample's README states that bird identification is "intentionally mocked (no LLM, no CV)".[7][29]

Use with AI models

At the announcement, UploadVR wrote that developers could send the camera imagery to a third-party multimodal AI model. Because the toolkit would not support Meta AI, they would have to start a continuous audio stream to and from the glasses and send camera images "to their own AI model of choice, at their own cost", which would affect battery life.[10] Meta's FAQ says developers "can process data locally or via cloud/edge platforms", while the glasses must still be paired through the Meta AI app.[9] Partner apps described by Meta use the camera feed for object recognition, text recognition, plant identification and visual positioning (see the table below).[13] Connecting a service to Meta AI itself is a separate developer preview, Meta AI Connectors, which turns a service's API into tools that the assistant can call. WebMCP, also in developer preview, lets web apps on Meta Ray-Ban Display define which of their features and actions Meta AI can control.[9][7]

For building apps, Meta's documentation describes three levels of AI help. Plugins for Muse Code, Claude Code and Codex install from the SDK's GitHub repositories, and checked-in instruction files serve GitHub Copilot, Cursor and tools that read AGENTS.md. A hosted Wearables Model Context Protocol server needs no token or other authentication and provides two search tools: search_dat_docs for the toolkit's guides, API reference and code examples, and search_webapps_docs for the Display Web Apps documentation. An llms.txt index serves the full API reference.[30][31] The iOS changelog lists these configuration files under version 0.5.0.[14]

Distribution and publishing

Developer mode, which a user enables in the Meta AI app by tapping the app version number five times, lets an unpublished app register with the user's glasses without publishing review. Only one third-party app can stay registered in developer mode; registering another unregisters the first.[32][16]

A project in the Meta Wearables Developer Center holds the Wearables application ID that builds need in order to register outside developer mode, the app's name and icon, and justifications for the permissions it requests, which are "for Meta's internal review only".[33] Every integration has one private, invite-only release channel, named Beta by default, that distributes one version at a time to testers invited through the email address of their Meta account.[15] Meta's May 2026 announcement said that toolkit builds could be shared through release channels "with up to 100 testers"; the current documentation instead tells developers to check the channel's Users tab for its tester limit.[6][15]

Under the developer terms, an integration "must be approved following the Integration Review before it can be enabled and generally released".[34] As of November 2026, Meta's FAQ says that two discovery surfaces are coming, select experiences found directly on Meta Ray-Ban Display and a curated list in the Meta AI app, and that they will expand as Meta begins taking submissions; its "Get discovered on AI glasses" page says Meta is "currently starting with a curated showcase".[9][35] Developers everywhere can download the SDK, but according to the FAQ only those in countries where Meta's AI glasses are supported get its full capabilities, including the Wearables Developer Center.[9]

Policies and privacy

The SDK repositories state that using the toolkit means agreeing to the Meta Wearables Developer Terms, last updated October 6, 2025, and the Acceptable Use Policy, last updated September 22, 2026.[17][34][36] The policy applies whether or not an integration is published. It prohibits integrations that "surreptitiously collect recognizable audio or video content of the user or others" or enable "bypassing, tampering with, or obscuring hardware-level recording indicators (such as the capture LED)". It also bars using device sensors "for unique identification of people based on physical characteristics, such as voices and faces", with exceptions for specific uses such as accessibility apps given prior Meta approval, and it rules out encouraging covert filming or the use of sensors or recording in sensitive locations, and facilitating military, warfare or espionage activities.[36] Meta's acceptable use guide gives its design principle as "narrow purpose, short retention, obvious to bystanders" and says Meta reviews and monitors toolkit apps and may act without prior notice, up to suspending or terminating developer accounts.[37]

The developer terms limit the use of "Technology Data", any information from, about or associated with a person, device or unique identifier that a developer obtains from the toolkit or other Meta developer technology covered by the terms, to running, supporting and maintaining an integration "in order to securely provide or improve the experience requested by the end user" and to complying with the law. They prohibit selling, licensing, purchasing or renting it, using it for surveillance, attempting to re-identify or de-anonymize it, collecting it by automated means such as scrapers, and using it to process protected health information without a Healthcare Addendum. Developers need a privacy policy that explains their processing and how users can request deletion, and must delete the data when a user asks or deletes their account unless the law requires keeping it. Experimental features "cannot be incorporated into any production build unless permitted by Meta in writing".[34] The SDK's READMEs also say that Meta may collect information about how users' devices communicate with the developer's app; this analytics collection is on by default and can be switched off with an Info.plist key on iOS or a manifest entry on Android.[17][18] Meta's telemetry documentation lists device identifiers, firmware versions, session durations, error types and success or failure flags among the data collected, and version 0.9.0 added a separate opt-out for the SDK's crash reporting.[38][8][14]

Documented apps and partners

Meta's September 2025 announcement included testimonials from early partners, among them HumanWare, L+R and Pixel and Texel, and an April 2026 post described a first wave of third-party integrations, saying that some of them would begin shipping that day without naming which.[4][13]

Developer or app Documented use Date described
18Birdies Golf app experimenting with real-time yardages and club recommendations September 2025[4][10]
Be My Eyes Service for blind and low-vision users; its chief executive said the toolkit could help with enterprise deployments September 2025[4]
Disney Imagineering Research and development prototypes giving guests tips in Disney parks September 2025[4][10]
Microsoft Seeing AI Visual assistant for blind people, paired with the glasses through the toolkit September 2025[4][10]
Twitch and Logitech's Streamlabs First-person livestreaming; Streamlabs also cited dynamic overlays and multistreaming September 2025[4][10]
Simply Draw (iOS) Time-lapse recording of drawings with step-by-step audio instruction April 2026[13]
Planta (iOS) Identifies plant species with the glasses camera and recommends care based on lighting, pot size and soil type April 2026[13]
OOrion (iOS) Voice activation, camera input, object recognition and text recognition with spatial audio for blind and low-vision users April 2026[13]
Aira Professional visual interpreters give live spoken guidance from the wearer's camera feed April 2026[13]
MultiSet AI (prototype) Streams camera frames to its visual positioning system for real-time location tracking "even without full 6DoF" April 2026[13]
SmartSight (prototype) Luna, a study coach that uses the camera and "contextual analysis" to track what students work on April 2026[13]

Supported devices and platforms

As of November 2026, the setup documentation lists Ray-Ban Meta glasses (Gen 1 and Gen 2), Ray-Ban Meta Optics glasses, Meta Glasses, Meta Ray-Ban Display, Oakley Meta HSTN and Oakley Meta Vanguard.[32] The FAQ says new SKUs of these devices are supported as they become available and that capability availability varies by device.[9] Each SDK release needs minimum versions of the Meta AI app and the glasses firmware; version 1.0.1 needs Meta AI app V292 and glasses firmware V128. Meta also gates some capabilities per user on its servers, so meeting the version requirements does not guarantee that a capability is available.[12]

The SDK supports iOS 17.2 and later with Xcode 26.4 or later, and Android 10 and later with Android Studio Flamingo or later; Android apps need Kotlin 2.2 or later because the toolkit is compiled with Kotlin 2.2.[32]

See also

References

  1. ↑ 1.0 1.1 1.2 1.3 1.4 1.5 "Integration overview". Meta Wearables Developers. Meta Platforms. https://wearables.developer.meta.com/docs/develop/dat/build-overview/. Retrieved 2026-11-01.
  2. ↑ 2.0 2.1 2.2 2.3 2.4 "Display access overview". Meta Wearables Developers. Meta Platforms. https://wearables.developer.meta.com/docs/develop/dat/display-overview/. Retrieved 2026-11-01.
  3. ↑ 3.0 3.1 3.2 Ben Lang (2025-09-18). "New Meta Developer Tool Enables Third-parties to Bring Apps to its Smart Glasses for the First Time". Road to VR. https://www.roadtovr.com/meta-ray-ban-smart-glasses-third-party-app-sdk-device-access-toolkit/. Retrieved 2026-11-01.
  4. ↑ 4.00 4.01 4.02 4.03 4.04 4.05 4.06 4.07 4.08 4.09 "Introducing the Meta Wearables Device Access Toolkit". Meta for Developers. Meta Platforms. 2025-09-18. https://developers.meta.com/blog/introducing-meta-wearables-device-access-toolkit/. Retrieved 2026-11-01.
  5. ↑ 5.0 5.1 David Heaney (2025-12-04). "Meta's Smart Glasses SDK Is Now Available To Build With, But Not Yet To Ship". UploadVR. https://www.uploadvr.com/meta-wearables-device-access-toolkit-public-preview/. Retrieved 2026-11-01.
  6. ↑ 6.0 6.1 6.2 6.3 "The wait is over: Build for display glasses starting today". Meta for Developers. Meta Platforms. 2026-05-14. https://developers.meta.com/blog/build-for-display-glasses/. Retrieved 2026-11-01.
  7. ↑ 7.0 7.1 7.2 7.3 7.4 "Meta Connect Recap: How To Build For AI Glasses And Reach an Audience". Meta for Developers. Meta Platforms. 2026-09-24. https://developers.meta.com/blog/meta-connect-recap-ai-glasses/. Retrieved 2026-11-01.
  8. ↑ 8.0 8.1 8.2 8.3 8.4 8.5 8.6 8.7 8.8 "CHANGELOG.md - meta-wearables-dat-android". GitHub. Meta Platforms. https://github.com/meta/meta-wearables-dat-android/blob/main/CHANGELOG.md. Retrieved 2026-11-01.
  9. ↑ 9.0 9.1 9.2 9.3 9.4 9.5 9.6 9.7 9.8 "Frequently Asked Questions". Meta for Developers. Meta Platforms. https://developers.meta.com/wearables/faq/. Retrieved 2026-11-01.
  10. ↑ 10.0 10.1 10.2 10.3 10.4 10.5 10.6 David Heaney (2025-09-18). "Meta's New SDK Will Let Developers Build Apps For Its Smart Glasses". UploadVR. https://www.uploadvr.com/meta-wearable-device-access-toolkit-announced-smart-glasses-sdk/. Retrieved 2026-11-01.
  11. ↑ 11.0 11.1 David Heaney (2026-06-11). "Developers Are Building Impressive Apps For Meta Ray-Ban Display's HUD & Neural Band". UploadVR. https://www.uploadvr.com/meta-ray-ban-display-amazing-hud-apps/. Retrieved 2026-11-01.
  12. ↑ 12.0 12.1 12.2 "Version Dependencies". Meta Wearables Developers. Meta Platforms. https://wearables.developer.meta.com/docs/develop/dat/version-dependencies/. Retrieved 2026-11-01.
  13. ↑ 13.0 13.1 13.2 13.3 13.4 13.5 13.6 13.7 13.8 "Build Apps that See, Hear, and Respond: Explore What's Possible With Wearables Device Access Toolkit". Meta for Developers. Meta Platforms. 2026-04-01. https://developers.meta.com/blog/explore-whats-possible-with-wearables-device-access-toolkit/. Retrieved 2026-11-01.
  14. ↑ 14.0 14.1 14.2 14.3 "CHANGELOG.md - meta-wearables-dat-ios". GitHub. Meta Platforms. https://github.com/meta/meta-wearables-dat-ios/blob/main/CHANGELOG.md. Retrieved 2026-11-01.
  15. ↑ 15.0 15.1 15.2 "Manage versions and release channels in Meta Wearables Developer Center". Meta Wearables Developers. Meta Platforms. https://wearables.developer.meta.com/docs/develop/dat/set-up-release-channels/. Retrieved 2026-11-01.
  16. ↑ 16.0 16.1 "Permissions and registration". Meta Wearables Developers. Meta Platforms. https://wearables.developer.meta.com/docs/develop/dat/permissions-requests/. Retrieved 2026-11-01.
  17. ↑ 17.0 17.1 17.2 "Meta Wearables Device Access Toolkit for iOS". GitHub. Meta Platforms. https://github.com/meta/meta-wearables-dat-ios. Retrieved 2026-11-01.
  18. ↑ 18.0 18.1 "Meta Wearables Device Access Toolkit for Android". GitHub. Meta Platforms. https://github.com/meta/meta-wearables-dat-android. Retrieved 2026-11-01.
  19. ↑ "Start a camera stream". Meta Wearables Developers. Meta Platforms. https://wearables.developer.meta.com/docs/develop/dat/streaming/. Retrieved 2026-11-01.
  20. ↑ 20.0 20.1 "Camera stream processing". Meta Wearables Developers. Meta Platforms. https://wearables.developer.meta.com/docs/develop/dat/camera-stream-processing/. Retrieved 2026-11-01.
  21. ↑ "Capture high-quality photos". Meta Wearables Developers. Meta Platforms. https://wearables.developer.meta.com/docs/develop/dat/camera-capture/. Retrieved 2026-11-01.
  22. ↑ 22.0 22.1 "Use device microphones and speakers". Meta Wearables Developers. Meta Platforms. https://wearables.developer.meta.com/docs/develop/dat/microphones-and-speakers/. Retrieved 2026-11-01.
  23. ↑ 23.0 23.1 "Receive input events from glasses and Meta Neural Band". Meta Wearables Developers. Meta Platforms. https://wearables.developer.meta.com/docs/develop/dat/inputs/. Retrieved 2026-11-01.
  24. ↑ 24.0 24.1 "Stream motion data from glasses sensors". Meta Wearables Developers. Meta Platforms. https://wearables.developer.meta.com/docs/develop/dat/motion/. Retrieved 2026-11-01.
  25. ↑ 25.0 25.1 "Transcribe speech on the glasses". Meta Wearables Developers. Meta Platforms. https://wearables.developer.meta.com/docs/develop/dat/speech/. Retrieved 2026-11-01.
  26. ↑ "Respond to Hey Meta voice invocations". Meta Wearables Developers. Meta Platforms. https://wearables.developer.meta.com/docs/develop/dat/voice-invocations/. Retrieved 2026-11-01.
  27. ↑ "Read battery, wear, and thermal state from glasses". Meta Wearables Developers. Meta Platforms. https://wearables.developer.meta.com/docs/develop/dat/device-state/. Retrieved 2026-11-01.
  28. ↑ 28.0 28.1 "Mock Device Kit". Meta Wearables Developers. Meta Platforms. https://wearables.developer.meta.com/docs/develop/dat/mock-device-kit/. Retrieved 2026-11-01.
  29. ↑ "BirdSpotter - Meta Wearables Device Access Toolkit Sample". GitHub - meta/meta-wearables-dat-android. Meta Platforms. https://github.com/meta/meta-wearables-dat-android/tree/main/samples/BirdSpotter. Retrieved 2026-11-01.
  30. ↑ "AI-Assisted Development". Meta Wearables Developers. Meta Platforms. https://wearables.developer.meta.com/docs/develop/dat/ai-assisted/. Retrieved 2026-11-01.
  31. ↑ "DAT MCP". Meta Wearables Developers. Meta Platforms. https://wearables.developer.meta.com/docs/develop/dat/ai-assisted-mcp/. Retrieved 2026-11-01.
  32. ↑ 32.0 32.1 32.2 "Setup". Meta Wearables Developers. Meta Platforms. https://wearables.developer.meta.com/docs/develop/dat/getting-started-toolkit/. Retrieved 2026-11-01.
  33. ↑ "Manage projects". Meta Wearables Developers. Meta Platforms. https://wearables.developer.meta.com/docs/develop/dat/manage-projects/. Retrieved 2026-11-01.
  34. ↑ 34.0 34.1 34.2 "Meta Wearables Developer Terms". Meta for Developers. Meta Platforms. 2025-10-06. https://wearables.developer.meta.com/terms. Retrieved 2026-11-01.
  35. ↑ "Get discovered on AI glasses". Meta for Developers. Meta Platforms. https://developers.meta.com/wearables/explore/. Retrieved 2026-11-01.
  36. ↑ 36.0 36.1 "Meta Wearables Developer Acceptable Use Policy". Meta for Developers. Meta Platforms. 2026-09-22. https://wearables.developer.meta.com/acceptable-use-policy. Retrieved 2026-11-01.
  37. ↑ "Acceptable use". Meta Wearables Developers. Meta Platforms. https://wearables.developer.meta.com/docs/develop/dat/acceptable-use/. Retrieved 2026-11-01.
  38. ↑ "Telemetry". Meta Wearables Developers. Meta Platforms. https://wearables.developer.meta.com/docs/develop/dat/telemetry/. Retrieved 2026-11-01.
Retrieved from "https://vrarwiki.com/index.php?title=Meta_Wearables_Device_Access_Toolkit&oldid=53393"