The Meta Ray-Ban Display SDK, explained
What the Meta Ray-Ban Display SDK actually is in 2026: Web Apps vs the Meta Wearables Device Access Toolkit, what each can and cannot do, and which one to build on.
TL;DR: "The Meta Ray-Ban Display SDK" is really two separate paths, both in developer preview since May 14, 2026: Web Apps (standalone HTML/CSS/JS rendered on the glasses, distributed by HTTPS URL, no camera) and the Meta Wearables Device Access Toolkit (a native iOS/Android SDK that extends your phone app onto the glasses, with camera and mic). Most independent developers should build Web Apps; you only need the native toolkit if you need the camera or microphone.
The two paths
Meta documents both at wearables.developer.meta.com. They are not interchangeable, and they answer different questions.
Web Apps: the standalone path
A Web App is a standard browser app hosted at a public HTTPS URL and rendered directly on the glasses display. No native code, no app review, no store listing. If you can build a web page, you can build one. This is the path GlassKit is built around, and the one most independent developers should take.
Meta Wearables Device Access Toolkit: the native path
A native SDK for Swift (iOS) and Kotlin (Android) that extends an existing mobile app onto the glasses: your phone app keeps running and gains access to the glasses' hardware, including the camera and microphone, and can draw UI on the display. Choose it when your product is really a phone app that uses the glasses as a sensor and display surface.
Capability comparison
| Capability | Web Apps | Meta Wearables Device Access Toolkit |
|---|---|---|
| Language / stack | HTML, CSS, JavaScript (any web framework) | Swift (iOS), Kotlin (Android) |
| Runs | Standalone on the glasses | As an extension of your phone app |
| Display | 600 × 600, additive, monocular (right lens) | The same display, drawn from the phone app |
| Camera | No | Yes |
| Microphone / audio capture | No | Yes |
| Motion + orientation sensors | Yes (DeviceMotion / DeviceOrientation) | Yes |
| Location | Yes (navigator.geolocation, via the paired phone) | Yes |
| Storage | localStorage / sessionStorage (5 MB) | Your app's own storage |
| Text input | No | Handled in your phone app |
| Distribution today | Public HTTPS URL, developer mode | Developer preview; select partners |
| App store | Not yet (Meta: broad publishing planned 2026) | Not yet |
The constraints that shape Web App design
- 600 × 600, one screen. The entire app is a single square viewport. No scrolling chrome, no multi-page site.
- Additive display. The display adds light to the world, so black renders as transparent. Apps are designed dark-first with bright, high-contrast foreground elements. The display is monocular (right lens), roughly 20° field of view, up to 5,000 nits.
- Input is Arrow keys + Enter. The Meta Neural Band (an EMG wristband) and the temple touch surface reach your app as standard arrow-key and Enter events; the pinch is the select gesture. There is no cursor, no touchscreen, and no raw gesture API for Web Apps. This also means you can develop in a desktop browser with the keyboard.
- No camera, no mic, no text input, no back-navigation API. Design around glanceable output and D-pad choices, not data entry.
- Minimum versions: glasses software v125+, Meta AI app v272+.
Why the input model is good news
Arrow keys + Enter means your entire app is testable in Chrome with
no hardware. GlassKit UI's useDpad() consumes the same events on
both surfaces, so the browser build and the on-glasses build behave
identically.
The hardware, briefly
The Meta Ray-Ban Display is $799 including the Meta Neural Band and is US-only as of mid-2026 (per meta.com). You do not need the hardware to start: a Web App runs in a normal browser at 600 × 600 with arrow-key simulation, and Chrome DevTools can fake motion, orientation, and GPS.
Which should you build on?
- You need the camera or microphone: the Meta Wearables Device Access Toolkit. No other option.
- Anything else (utilities, navigation, fitness, reference, AI assistants): Web Apps. Faster to build, no native toolchain, distributed by URL, built with the stack you already know.
If you're going the Web Apps route, the practical next steps: the end-to-end build guide, the free GlassKit UI component library, or generating your first app from a prompt.
Related reading
How to build a Meta Ray-Ban Display app
The complete guide to building, previewing, and shipping an app for Meta Ray-Ban Display glasses: the two SDK paths, the Web Apps constraints, and the deploy-to-glasses flow.
How to publish a Meta Ray-Ban Display app
The 2026 developer-preview publishing flow for Meta Ray-Ban Display Web Apps: host at HTTPS, enable developer mode, add by URL, and what 'no app store yet' actually means.