meta-dat-android-integration

Integrates the Meta Wearables Device Access Toolkit into Android apps with Gradle, Kotlin, and DatResult flows.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/shotcowboystyle/meta-wearables-ops-plugin --skill meta-dat-android-integration-shotcowboystyle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-dat-android-integration
Source: https://github.com/shotcowboystyle/meta-wearables-ops-plugin/tree/main/.agent/skills/meta-dat-android-integration
Command: npx skills add https://github.com/shotcowboystyle/meta-wearables-ops-plugin --skill meta-dat-android-integration-shotcowboystyle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Integrating Meta smart glasses into an Android app requires exact Maven artifacts, Manifest configuration, session lifecycle handling, and version-specific API knowledge that is easy to get wrong, especially across the 0.9 migration. ## Core Features & Use Cases - Guided Android Integration: Resolves the correct mwdat-core, mwdat-camera, mwdat-display, and mwdat-mockdevice artifacts, then walks through initialization, registration, sessions, and capability attachment. - 0.9 Migration Review: Flags removed APIs such as direct stream routes, old DisplayComponent/VideoScope builders, and outdated DAM metadata using a bundled migration fixture. - Evidence Separation: Enforces a strict evidence matrix that keeps Gradle builds, MockDevice fixtures, connected-device runs, and physical-glasses proof clearly separated. - Use Case: When adding camera streaming to a Kotlin app for Meta glasses, use this Skill to configure Gradle dependencies, implement typed DatResult state flows, attach the camera after session start, and produce a test plan covering mock and physical devices. ## Quick Start Ask the assistant to integrate the Meta Wearables DAT SDK into your Android project and review the Gradle, Manifest, and session lifecycle setup.

Frequently Asked Questions about meta-dat-android-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate the Meta Wearables DAT SDK into an Android app?

Resolve the required Maven modules (mwdat-core, mwdat-camera, mwdat-display, mwdat-mockdevice), call Wearables.initialize(context) once, then create and start a DeviceSession before attaching capabilities like Camera or Display. Expose typed registration, permission, and failure states to your UI using Flow and StateFlow.

What changed in the Meta DAT Android 0.9 migration?

Version 0.9 replaces direct stream APIs with addCamera() and camera.stream, updates Display to builder blocks with button groups and tap callbacks, and removes old DisplayComponent and VideoScope shapes. Older upstream examples still reference 0.8.0 coordinates and Session wording, so verify symbols against the resolved artifacts.

Does the Meta DAT Android SDK support testing without physical glasses?

Yes, the mwdat-mockdevice module provides lifecycle, media, and permission fixtures for deterministic testing, including R8 consumer-rule checks in release builds. However, mock results must never be presented as connected-transport or physical-glasses proof.

Why should I avoid getOrThrow() with DatResult in Android DAT apps?

DatResult<T,E> carries typed failure information that user-facing paths should handle gracefully rather than throwing. Using getOrThrow() bypasses the typed error contract and can crash the app on registration, permission, or session failures.

Can I reuse iOS Meta DAT code or results for my Android integration?

No, Kotlin signatures and Android support must never be inferred from iOS code, and iOS test results cannot be converted into Android proof. Parity comparisons should label symbols explicitly as same-concept or platform-specific.