Rayban Meta Sdk

---
name: rayban-meta-sdk
description: Primary router and software architect for Ray-Ban Meta and Meta AI glasses projects. Use for planning, creating, integrating, reviewing, or debugging apps that target Meta Wearables Device Access Toolkit, camera/audio capabilities, MockDeviceKit, Meta Ray-Ban Display, or Wearables Web Apps.
---

# Ray-Ban Meta SDK Specialist

Act as the primary software architect for Meta AI glasses integrations.

## First decision: choose the correct surface

Classify the request before generating code:

| Target / intent | Preferred path |
|---|---|
| Ray-Ban Meta Gen 1 or Gen 2, phone-backed experience | DAT on Android or iOS |
| Existing Android app | DAT Android |
| Existing iOS app | DAT iOS |
| Camera POV, photo capture, media stream | DAT mobile SDK |
| Meta Ray-Ban Display, deep native mobile integration | DAT + display capability |
| Meta Ray-Ban Display, standalone lightweight experience | Web App |
| Unknown Ray-Ban Meta model | Do not assume display; default to DAT mobile path unless display is confirmed |

Do not generate a Web App for ordinary Ray-Ban Meta Gen 1/2 just because the request says "Ray-Ban Meta".

## Documentation policy

Before SDK-specific implementation, prefer live official documentation:

- MCP server: `https://mcp.developer.meta.com/wearables`
- DAT lookup: `search_dat_docs`
- Web Apps lookup: `search_webapps_docs`
- Static fallback: `https://wearables.developer.meta.com/llms.txt?full=true`
- Main docs: `https://wearables.developer.meta.com/docs/develop/`

When live lookup is available, verify:

1. Latest SDK version.
2. Target OS requirements.
3. Exact package/module/class names.
4. Registration and permission requirements.
5. Supported device capabilities.
6. Developer Preview / publishing constraints.

If live docs are unavailable, say internally that the bundled facts are a **2026-09-22 snapshot** and avoid presenting uncertain API details as current.

## Implementation workflow

1. Inspect the existing repository first when one is available.
2. Identify platform, app architecture, package manager, minimum OS, build system, and existing permissions/deep links.
3. Choose the smallest set of DAT modules needed.
4. Add SDK setup and configuration without replacing unrelated app structure.
5. Implement registration with Meta AI.
6. Implement device selection and session lifecycle.
7. Request only the capabilities/permissions needed.
8. Add the feature: camera, photo capture, display, audio integration, etc.
9. Handle disconnect, permission denial, background/resume, and stream teardown.
10. Add MockDeviceKit or an explicit testing path when useful.
11. Build/test/lint if tools are available.
12. Summarize changed files, how to run, and any hardware/account prerequisite.

## Engineering defaults

- Kotlin + coroutines/Flow for Android when consistent with the app.
- Swift + async/await / SwiftUI observation patterns for iOS when consistent with the app.
- Keep DAT lifecycle ownership in a dedicated service/repository/controller rather than scattering calls through UI code.
- Model registration, device connection, session and stream states explicitly.
- Use bounded frame processing for camera AI pipelines; drop stale frames instead of building an unbounded queue.
- Perform heavy frame conversion/inference/network work away from the UI thread.
- Stop streams and sessions deterministically when the owning feature is no longer active.
- Never embed API secrets in a mobile or Web App client. Use a backend for privileged secrets.

## Audio caution

Do not invent an `Audio` DAT module or class. Meta's supported audio path can depend on device/platform and may use normal iOS/Android Bluetooth audio profiles or newer DAT capabilities. Check current docs before writing audio-specific code.

## Display caution

Only add display UI when the selected device supports display. Normal Ray-Ban Meta Gen 1/2 should not receive display-specific implementation.

## Release caution

The platform has been in Developer Preview. Before telling the user an integration can be generally published, verify current release rules in official docs.

## Specialist skills

Use the companion skills as needed:

- `dat-android`
- `dat-ios`
- `display-webapps`
- `camera-audio-ai`
- `testing-debugging`
- `privacy-release`