Meta this month opened developer access to the display on Meta Ray-Ban Display glasses, releasing two distinct build paths in developer preview: an updated native mobile SDK for iOS and Android, and an entirely new Web Apps route for building standalone experiences with standard HTML, CSS, and JavaScript. The announcement, dated May 14, 2026, marks the first time third-party developers can target the built-in display on a consumer AI glasses product that is already on sale.

Why this matters for the wearables platform

Until now, developers building on Meta's AI glasses had access to camera, audio, and voice inputs. Visual output to the wearer was not part of the developer toolkit. That gap closes with today's release. According to Meta, the addition of display capabilities means developers can present information directly in the moment - not as an audio response, not through a companion smartphone notification, but visually overlaid within the lens the user is already wearing.

The glasses in question are not a prototype or a limited developer device. Meta Ray-Ban Display, which launched at the company's Connect conference on September 17, 2025, at a retail price of $799, is available to consumers at Best Buy, LensCrafters, Sunglass Hut, Ray-Ban Stores, and Meta Lab locations across the United States. Developers building against this SDK are therefore targeting a device that real users are wearing in the world - a detail Meta specifically highlighted as an advantage over previous wearable development environments.

The Device Access Toolkit and what it can now do

The first build path runs through the Meta Wearables Device Access Toolkit, a native mobile SDK for iOS and Android that previously gave developers access to camera, audio, and voice functionality on Meta's AI glasses. According to Meta, display capabilities have now been added to that toolkit. Using Swift for iOS or Kotlin for Android - toolchains developers already know - it is now possible to extend an existing mobile app onto the glasses display.

The display components available to developers through the toolkit include text, images, lists, buttons, and video playback. Combined with the pre-existing camera, audio, and voice capabilities, the Device Access Toolkit gives iOS and Android developers a hardware integration layer that Meta describes as offering more depth than any other AI glasses SDK currently on the market.

The toolkit is available through GitHub repositories for both iOS and Android, and accompanying documentation covers the integration process in detail. Developers with an existing mobile app who want to extend it onto the glasses display are directed to this path.

Web Apps: a browser-native build path

The second path is new to the ecosystem entirely. Meta today introduced Web Apps for Meta Ray-Ban Display glasses - a route that requires no proprietary framework and no new programming language. Developers build using standard web technologies: HTML, CSS, and JavaScript. According to Meta, Web Apps have access to motion and orientation data, phone GPS, input from the Meta Neural Band, and local storage.

The iteration speed for this path is notably faster than the native SDK approach. Developers can build and preview experiences directly in a browser before deploying to the glasses via a URL. Meta positions this path as suited to rapid prototyping, lightweight utilities, and categories of on-device experience that do not yet exist. Example use cases cited by Meta include games, transit tools, cooking guides, grocery lists, and instrument practice aids.

A starter kit for Web Apps is available on GitHub and is compatible with AI coding tools including Claude Code, Cursor, and GitHub Copilot, according to Meta's announcement.

The gesture input layer: surface EMG via Meta Neural Band

Display output is only one side of the developer access story. Developers building experiences for Meta Ray-Ban Display also gain access to gesture input through the Meta Neural Band - the EMG wristband that ships with every pair of Meta Ray-Ban Display glasses.

Meta Neural Band uses surface electromyography (EMG) to read the electrical signals created by muscle activity at the wrist, translating subtle finger and hand movements into device commands. According to Meta, the research underpinning this technology involved nearly 200,000 participants. All raw EMG processing happens on the device itself; only discrete events - the equivalent of a "click" - are transmitted from the wristband to the glasses, which is relevant for latency and privacy considerations.

The band supports up to 18 hours of battery life and carries an IPX7 water resistance rating. Its electrodes are coated with diamond-like carbon and reinforced with Vectran, a woven mesh material also used in the crash pads of the Mars Rover. For developers, the Neural Band introduces an input model that does not depend on touchscreens, voice commands, or capacitive touch. Experiences can respond to simple hand gestures, giving users immediate, low-profile control without requiring speech or physical contact with the glasses frame.

Meta VP of Wearables Alex Himel said at CES 2026 in January that "once you start using the band regularly, you want it to control more than just your AI glasses." Meta had already demonstrated Garmin integration at that event, connecting the Neural Band to the Garmin Unified Cabin car infotainment system as a proof of concept. Opening the band as a developer input within the glasses SDK extends that ambition into the wider third-party app ecosystem.

What developers can build

According to Meta's announcement, the use cases now accessible to developers span several categories. Information overlays represent the most immediate territory - real-time data displays like live scores, status updates, or contextual information surfaced from a connected app. Micro-apps, utilities, and experimental interactions form a second category, with the Web Apps path particularly suited to this kind of lightweight, purpose-specific tooling.

Streaming media is listed as a supported use case, though the resolution and display characteristics of the Meta Ray-Ban Display lens constrain what this means in practice. The in-lens display in the consumer product operates at 600x600 pixels and is built into the right lens using Transitions adaptive lens technology. It is private - not visible to people near the wearer.

The developer preview also includes distribution mechanisms. According to Meta, developers can share Web Apps via password-protected URLs and can distribute Device Access Toolkit builds through release channels with up to 100 testers - a meaningful number for early-stage testing without requiring a public app store submission.

Context: the advertising and marketing angle

For the marketing community, the opening of the Meta Ray-Ban Display to third-party developers is a structural shift in how brands and publishers can reach people wearing connected devices. PPC Land has been tracking the advertising implications of Meta's AI glasses since September 2024, when Meta announced real-time language translation, visual question answering, and memory assistance for the Ray-Ban Meta glasses - capabilities that raised questions about how wearable data might intersect with ad targeting.

The expansion of the Meta AI assistant to European markets in November 2024 extended the reach of the platform further, with the rollout to France, Italy, Ireland, and Spain bringing voice-activated AI functionality in French, Italian, and Spanish.

With display developer access now open, the glasses platform becomes something closer to an app ecosystem - one where utility apps, navigation tools, and information overlays can be built by third parties. Whether and how advertising enters that layer is not addressed in today's announcement. Meta has not indicated that the developer preview includes advertising inventory or ad delivery mechanisms. What today's release does do is establish the technical infrastructure on which a future content and commerce layer could be built.

The scale of the existing Meta Ray-Ban glasses user base is relevant context here. Meta Ray-Ban Display went on sale in September 2025, and Meta has described demand for in-person demos as strong. The underlying Ray-Ban Meta platform - the audio-only AI glasses that preceded the Display model - is described by Meta as the number-one selling AI glasses product. Developers building for the Display are therefore addressing a hardware install base that already exists, not one that has to be created.

Technical constraints and rollout timeline

According to Meta, availability is rolling out starting today, over the coming weeks, and is not yet complete. Developers are encouraged to start building early to work through bugs and shape what the platform becomes. Meta operates a Developer Center where developers can submit feedback and report issues.

The developer preview framing carries implications for stability and supported features. Web Apps and the updated Device Access Toolkit are both described as preview releases, meaning the APIs and capabilities may change before reaching a more stable state. Meta is using early adoption pressure as a mechanism for platform refinement - a standard approach for wearable and emerging-compute SDKs, though it places burden on developers to track changes.

Neither the Web Apps path nor the Device Access Toolkit requires developers to purchase specialized hardware or dev kits. The consumer Meta Ray-Ban Display product, priced at $799, functions as the development target device.

Timeline

  • September 2023: Meta launches first-generation Ray-Ban Meta smart glasses.
  • September 25, 2024: Meta announces AI features for Ray-Ban Meta including real-time translation and memory assistance; advertising implications discussed at PPC Land.
  • November 18, 2024: Meta expands the AI assistant to France, Italy, Ireland, and Spain on Ray-Ban Meta glasses with French, Italian, and Spanish language support.
  • September 17, 2025: Meta announces and launches Meta Ray-Ban Display and Meta Neural Band at Connect 2025, priced at $799, available at US retailers including Best Buy, LensCrafters, Sunglass Hut, and Ray-Ban Stores.
  • January 6, 2026: At CES 2026, Meta demonstrates Neural Band teleprompter mode, EMG handwriting for WhatsApp and Messenger, and a Garmin Unified Cabin automotive integration proof of concept.
  • March 31, 2026: Meta announces Ray-Ban Meta Optics Styles - the Blayzer Optics and Scriber Optics frames - built for prescription lenses, starting at $499.
  • May 14, 2026: Meta opens developer access to the Meta Ray-Ban Display glasses display, releasing the updated Device Access Toolkit for iOS and Android and launching Web Apps as a new build path using HTML, CSS, and JavaScript.

Summary

Who: Meta, through its developer platform, and third-party iOS, Android, and web developers building for the Meta Ray-Ban Display glasses platform.

What: Meta has opened two developer preview build paths for targeting the display on Meta Ray-Ban Display glasses - an updated native mobile SDK (the Meta Wearables Device Access Toolkit, supporting Swift for iOS and Kotlin for Android) and a new Web Apps route based on standard HTML, CSS, and JavaScript. Both paths also expose gesture input through the Meta Neural Band EMG wristband. Developers can share builds with up to 100 testers during the preview period.

When: The announcement was made on May 14, 2026, with availability rolling out starting that day over the coming weeks.

Where: The developer resources are accessible via GitHub repositories and the Meta Developer Center at developer.meta.com/wearables. The target device - Meta Ray-Ban Display - is a consumer product on sale in the United States at $799.

Why: Meta is opening the display layer to developers to accelerate the creation of third-party experiences on a consumer AI glasses platform with an existing user base. By allowing developers to build with familiar tools rather than requiring new languages or frameworks, Meta is reducing friction for adoption. The move expands what can be done on the glasses beyond Meta's own first-party features and positions the device as a platform - rather than just a product - ahead of a period of intensifying competition in the AI wearables market.

Two paths, one choice

The decision between the two build paths comes down to what a developer already has. An existing iOS or Android app that could benefit from a display extension points toward the Device Access Toolkit - the native path with deep hardware access. Building something new, or moving quickly to test an idea, points toward Web Apps, which removes the toolchain setup overhead and allows for browser-based iteration before any glasses hardware is needed. Both paths land in the same place: an experience delivered to a device worn on a consumer's face.

That framing - experiences delivered to devices people are already wearing - is likely to shape how marketers and product teams think about the Meta Ray-Ban Display platform in the months ahead. Unlike mobile apps, which must compete for attention on a screen the user actively chooses to look at, display glasses experiences are ambient. They surface at a glance, occupy a context-specific moment, and disappear. The developer tools Meta is releasing today set the technical foundation for what kinds of experiences that context can support.

Share this article
The link has been copied!