Overview

The Visor Development Kit (VDK) is how other software uses Meta's glasses through Visor. Visor is an Android app that replaces the Meta AI app as the phone side of Ray-Ban Meta glasses, the Meta Ray-Ban Display and the Meta Neural Band: it holds their Bluetooth and Wi-Fi links and speaks their protocol. The VDK gives that link to your code. How that protocol works, down to the bytes, is in the protocol reference.

Who it is for

• Android apps that want the glasses' camera, their status, the band's gestures or the Display.
• Web apps on the Meta Ray-Ban Display, which reach the VDK from JavaScript through the Display's browser.
• Scripts and tools on a computer: automations, prototypes, a test harness, an AI agent that drives the glasses. They reach Visor through adb or over the network.
• Visor's own features, which can be built and tried outside Visor first.

How it works

flowchart LR
    app["Your Android app"] -- "VDK library" --> visor
    computer["Your computer"] -- "adb, JSON-RPC" --> visor
    agents["Programs and AI agents"] -- "WebSocket, MCP" --> visor
    web["A web app on the Display"] -- "the Display's browser" --> visor
    visor(["Visor, on the phone"]) -- "Bluetooth, Wi-Fi Direct" --> glasses["Glasses and Neural Band"]

Everything the VDK does is a method (a request with one answer, like camera.photo), a topic (a stream of events, like band.gestures) or a feed (a stream of binary records, like the live video of camera.live). Each has a name, a scope, and the protocol version that added it. The kit-protocol module defines all of them, and protocol/api/openrpc.json describes them for any language.

There are four ways in, with the same methods and topics:

• The Android library (com.macedonga.visor:kit). Your app binds to Visor's VDK service. Visor knows which app is calling from Android itself, by its package and its signing certificate, so nothing can pretend to be your app.
• The adb socket. Visor listens on a local socket that only adb's shell user may use. The visor command on your computer, or any program that speaks JSON-RPC, reaches it with adb forward.
• The network door. JSON-RPC over a WebSocket, and MCP for AI agents, on the phone or the local network, for clients the person makes a token for. See The network door.
• The Display's browser. A web app on the Meta Ray-Ban Display connects with the TypeScript client's Visor.connectGlasses(). See Web apps on the Display.

The person stays in charge:

• Scopes say what each app, client or web app may do. The person grants them and can take them back in Settings. See Scopes and consent.
• Developer mode in Visor opens the adb socket for the computer-side tools. Apps never need it.

The glasses' own safeguards stay in place: the capture light turns on for every photo and video the VDK takes.

What it can do

Compared with Meta's Wearables Device Access Toolkit

Meta's toolkit (DAT) works through the Meta AI app and a Meta-signed program on the glasses. The VDK works through Visor instead, so the trade-offs differ:

On the glasses, layouts come from the session DAT opens with Meta's toolkit app on the Display: Visor installs that app and sets the glasses up once per pair. Motion comes from the glasses' own sensor service, and the band's and the touchpad's gestures from a session without the toolkit app, so neither puts anything on the screen. Porting from Meta's DAT maps each part of DAT to the VDK.

Roadmap

1. VDK 0.1: the glasses' status and pairs, the camera and captures, the Neural Band, the Display's teleprompter, the visor command and FakeVisor.
2. Voice and the assistant: phrases routed to apps ("Hey Meta, ask My App..."), apps started by a phrase, tools for the assistant's model, answers in the glasses' own voice, lines the glasses say unasked, transcripts, notifications on the Display, the glasses' settings and the assistant's history.
3. The network: JSON-RPC over WebSocket and an MCP server on the phone, webhooks, Python and TypeScript clients, and raw access to the glasses' services for research.
4. The Display: Briefing cards with details, pages, charts, clicks and live updates; the VDK in the Display's web apps, with their WebMCP tools for the assistant (Web apps on the Display); and the Neural Band shared with the phone, so apps get its gestures, wrist motion and vibration while the Display keeps using it.
5. The Display's toolkit session: layouts with video, inputs, motion with nothing on the screen, and the Display's own speech recognition.

Next: the first public release, on Maven Central, npm and PyPI.