ONLINEAGENT_OPS 2026.Q3 HOME HUBSMODELSBUILDINGCOMPANIESFILMMAKINGSECURITYLIVING WITH ITSKILLSALL HUBS, ONE TERMINAL → ARTICLES CRAFT RECORD BLOG TOOLS SKILLS SEARCH /
HOME›ARTICLES›HOW TO BUILD FOR META RAY-BAN DISPLAY GLASSES
ARTICLES · GUIDEADVANCED

How to Build for Meta Ray-Ban Display Glasses

Meta opened the display to developers in May 2026: a native SDK, or plain HTML deployed by URL. The two paths, the wristband input, and the preview limits.

READ5 min
WORDS918
SECTIONS5
TYPEGUIDE
CHECKED1 OCT 26

You can put a web page on Meta’s display glasses with HTML, CSS and JavaScript, and deploy it by URL. Meta opened developer access to the Meta Ray-Ban Display screen on 14 May 2026, with two build paths and no new language to learn. On 24 September 2026 the developer toolkit left preview and reached version 1.0.12

TL;DR — THE SHORT VERSION
  • Two paths: a native mobile SDK, or web apps in plain HTML, CSS and JavaScript.
  • The web path deploys by URL. Meta: “build and preview in your browser, then deploy to your glasses via a URL”.
  • Input is a wristband, not a touchscreen — gestures read by surface electromyography.
  • It is out of preview. Meta says toolkit 1.0 “has officially launched” (24 September 2026) and that web apps for the display are available.
  • Where the glasses are sold: the US, Canada and the UK, with France, Italy and Germany from 13 October 2026, according to Meta.
  • Listing your app is not open yet. Meta says details on getting apps into its new app-discovery spaces are “coming soon”.
  • During the preview, sharing was capped: password-protected URLs for web apps, up to 100 testers for native builds.

The two paths

Meta’s own split, read at source 16 Sep 2026
Device Access ToolkitWeb Apps
LanguageSwift, KotlinHTML, CSS, JavaScript
Forextending an existing appbuilding something new
Deployrelease channelsa URL
Share withup to 100 testerspassword-protected URLs

Meta, Build for display glasses, 14 May 2026, read at source 16 Sep 2026: “Even in Developer Preview, you can share Web Apps via password-protected URLs and Device Access Toolkit builds via release channels with up to 100 testers.”

Meta’s own advice on choosing: “If you have an existing iOS or Android app and want to extend it onto the glasses display, start with the Device Access Toolkit. If you’re building something new — or just want to move fast with web tools — Web Apps is your path.”

TAKEAWAY

The web path is the interesting one: the glasses take an ordinary web page. That makes the barrier a URL rather than an app review.

What a web app can reach

More than a browser normally gets. Meta lists “access to motion and orientation data, phone GPS, input from the Meta Neural Band and local storage”, and describes the loop as fast “because it’s web-native”.

Its own list of what people might build: “games, transit tools, cooking guides, grocery lists, instrument practice”, and on the display side “Information overlays”, “Real-time data displays, like scores or status updates” and “Micro-apps, utilities, and experimental interactions”.

Meta even names the tools it expects you to write it with: the starter kit is for building “with your favorite AI coding tools including Claude Code, Cursor, GitHub Copilot, and more”.

The input model is the unfamiliar part

There is no touchscreen on your face. Meta: the glasses “support gesture controls powered by surface electromyography (EMG) via Meta Neural Band, enabling effortless input through subtle finger and hand movements.”

And what that means for design: “this opens up a new unique interaction model that doesn’t rely on touchscreens, voice, or capacitive touch. You can design experiences that respond to simple gestures, enabling more discrete, immediate control in real-world contexts without speaking or reaching for the glasses.”

That is a constraint before it is a feature. A layout that assumes a scroll, a keyboard or a pointer has nothing to fall back on here, and the accessibility questions that raises are on is your AI output usable.

DESIGNING FOR THE GLASSES · WHAT A WEB APP HAS
Meta’s own lists, side by side: what a web app can reach, and what the input model does not rely on.
WHAT A WEB APP CAN REACH
Yes: Input from the Meta Neural Band (gestures read by EMG)
Yes: Motion and orientation data
Yes: Phone GPS
Yes: Local storage
WHAT THE INPUT MODEL DOES NOT RELY ON
No: Touchscreens
No: Voice
No: Capacitive touch
Meta, Build for display glasses, 14 May 2026, read at source 16 Sep 2026: “access to motion and orientation data, phone GPS, input from the Meta Neural Band and local storage”, and an interaction model that “doesn’t rely on touchscreens, voice, or capacitive touch”.

The catch

The tools are finished; the shop window is not. In May Meta called this a preview, “rolling out over the coming weeks”. On 24 September 2026 it said: “After a year in developer preview, the Meta Wearables Device Access Toolkit 1.0 has officially launched.” Meta also announced a new UI Toolkit, a set of ready-made screen parts for the display.1

What is still missing is a way to be found. Meta says two “discovery surfaces” (places where owners browse and install apps) are coming, and that details on submitting apps to them are “coming soon”. Until then, sharing by link is the route.

Your audience is still limited to a few countries. Meta says the Display glasses went on sale in Canada and the UK on 23 September 2026, on top of the US, with pre-orders in France, Italy and Germany ahead of 13 October.3

The reassuring half of Meta’s pitch is that the hardware is not hypothetical: “You don’t need to build with a dev kit and imagine what might be possible—these glasses already exist.”

What this page could not verify

  • Whether it all works as described. Toolkit 1.0 is Meta’s announcement.First-hand: until 1 Oct 2026 this item read “Current availability. Announced as rolling out in May 2026; not re-checked with a device.” Meta has since announced version 1.0, quoted above.
  • Anything about performance. No figures published in the post read here.
  • Which glasses models the toolkit supports. Not stated on the Meta pages read for this update. Countries are now answered above.
  • Whether the 100-tester cap still applies after 1.0. Not stated.
  • Whether a web app works offline. Local storage is named; offline behaviour is not.
SOURCES
  1. 1Meta, Meta Connect 2026: The end-to-end recap, 24 Sep 2026, read at source 1 Oct 2026“After a year in developer preview, the Meta Wearables Device Access Toolkit 1.0 has officially launched.” On web apps: “Standard web APIs render on the built-in display with no native app or SDK required.” On the app listings: “More information on submitting web apps and apps built with the Device Access Toolkit for approval to appear on these surfaces is coming soon.” ↑a“After a year in developer preview, the Meta Wearables Device Access Toolkit 1.0 has officially launched.” On web apps: “Standard web APIs render on the built-in display with no native app or SDK required.” On the app listings: “More information on submitting web apps and apps built with the Device Access Toolkit for approval to appear on these surfaces is coming soon.” ↑b
  2. 2Meta, The wait is over: Build for display glasses starting today, 14 May 2026, read at source 16 Sep 2026.↑
  3. 3Meta, New Features for Meta Ray-Ban Display, 23 Sep 2026, read at source 1 Oct 2026“The glasses go on sale today in Canada and the UK, and pre-orders will progressively start today in France, Italy, and Germany, ahead of availability on October 13.” ↑

Added 1 October 2026: Meta, Meta Connect 2026: The end-to-end recap, 24 September 2026 · Meta, New Features for Meta Ray-Ban Display, 23 September 2026. Both read at source on 1 October 2026.

Developer tools change without notice.

Free printable AI cheat sheets, and AI news every week.

Sixteen one-page AI guides and checklists in one free PDF, no sign-up. And if you want to keep up, the newsletter covers what changed in AI each week, in plain English, with the sources.

SUBSCRIBE FREE ↗ GET THE CHEAT SHEET PACK
aipromptgeneer://$ about this siteAI PROMPT GENEERAI explained in plain English. Every claim links to its source, with the date it was checked.NEWSLETTERWhat changed in AI each week, in plain English.SUBSCRIBE FREE ↗AI PROMPT GENEER · MACHINE ASSISTANCE DISCLOSEDEVERY ARTICLE CARRIES ITS OWN CHECKED DATE