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.
TL;DR: There is no app store for the Meta Ray-Ban Display yet. "Publishing" a Web App in 2026 means: deploy it to a public HTTPS URL, and anyone with developer mode enabled in the Meta AI app can add it to their glasses from that URL. Meta says broad publishing is planned for 2026. A QR code is just a convenient wrapper around the URL, not an official Meta step.
The current state of publishing
Per Meta's developer docs (wearables.developer.meta.com), the Meta Ray-Ban Display platform has been in developer preview since May 14, 2026. What that means concretely:
- No public app store. You cannot list an app for the general public yet. Meta has said broad publishing is planned for 2026, with select partners distributing during the preview.
- Web Apps load by URL. A Web App is fetched live from a public HTTPS URL (plain HTTP is not supported). Whoever has the URL and developer mode can run your app.
- Updates are deploys. Because the app loads from your URL, you update it by deploying, exactly like a website. No resubmission, no review queue.
Publishing a Web App, step by step
Deploy to HTTPS. Any static-capable host works: Vercel, Netlify, Cloudflare Pages, GitHub Pages. The URL must be publicly reachable and HTTPS.
Enable developer mode in the Meta AI app (tap the app version a few times in Settings).
Add the app: Display Glasses settings → App connections → Web apps → Add a web app → enter your URL. The app appears in the glasses launcher.
Share it: send the same URL to anyone you want testing it. They repeat steps 2 and 3. A QR code that encodes the URL saves them the typing; that's a convenience layer (it's what GlassKit's publish button generates), not part of Meta's flow.
Minimum versions: glasses software v125+, Meta AI app v272+.
What to have ready for the store opening
The teams that win a new platform's catalog are the ones that are finished when the gate lifts. Being "finished" for the Meta Ray-Ban Display means more than a working 600 × 600 screen:
| Ready today | Why it matters at the gate |
|---|---|
| App deployed and stable at its URL | Store listing will point at a working product, not a repo |
| Tested on real hardware | Additive-display contrast and Neural Band feel can't be fully judged in a browser |
| Accounts, payments, and backend wired | Monetization can't be bolted on the week the store opens |
| A companion site | Users need somewhere with a keyboard to sign up and pay |
The GlassKit Stack exists for exactly this: it ships the companion site, auth, payments, and backend around your glasses app so the day publishing opens, you list a business, not a demo.
Publishing from GlassKit Studio
If you built your app in GlassKit Studio, publishing is one click: Studio hosts the app at a stable HTTPS URL (yourapp.glasskit.studio) and gives you the QR code that encodes it. The flow above is what that button automates.
Related reading
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.
Best framework for Meta Ray-Ban Display apps (2026)
The honest 2026 comparison of every way to build a Meta Ray-Ban Display app: vanilla Web Apps, Meta's AI toolkit, GlassKit UI, GlassKit Studio, and the GlassKit Stack.