Meta Just Opened Ray-Ban Display Glasses to Third-Party Developers. Here Is How It Works.

Meta has opened the Ray-Ban Display glasses to third-party developers for the first time. The new developer preview, announced May 14, gives outside developers two distinct paths for building apps that push content directly into the wearer's right-lens display. One path uses native mobile SDKs for iOS and Android. The other uses standard web technologies. Both support gesture input through Meta's Neural Band EMG wristband. This is the moment Ray-Ban Display stops being a Meta-only experience and starts becoming a platform.

Two Paths, One Display

The native path is the Meta Wearables Device Access Toolkit, a mobile SDK available for both iOS (Swift) and Android (Kotlin). This toolkit lets developers extend their existing mobile apps to the glasses display. If you already have an iOS or Android app and want to add a glasses layer on top of it, this is the route. The SDK handles the communication between your phone app and the in-lens display, so developers do not need to learn a new framework from scratch. They write display logic in the language they already know and let the toolkit handle the rendering pipeline to the glasses.

The web path is entirely new and arguably the more interesting development. Meta is allowing developers to build standalone experiences for Ray-Ban Display using standard HTML, CSS, and JavaScript. These Web Apps run directly on the glasses without requiring a companion mobile app. For web developers, this lowers the barrier to entry significantly. If you can build a website, you can build a glasses experience. The rendering constraints are different (you are targeting a small in-lens display rather than a phone screen), but the underlying technology stack is familiar.

Both paths expose the same input capabilities. Developers can respond to tap gestures on the glasses frame and, more significantly, to neural input from the Meta Neural Band. The EMG wristband reads electrical signals from your forearm muscles, translating subtle hand movements into discrete input events. This gives developers an input vocabulary beyond just tapping the frame, which opens up interaction patterns that would be impossible with touch alone.

What Developers Can Build

The developer preview supports real-time overlays, live data feeds, micro-apps, and utilities displayed on the in-lens screen. Think sports scores that update during a game, navigation prompts while cycling, workout metrics during a run, or quick-reference information for hands-busy tasks like cooking or repair work. The display is small and positioned in the peripheral vision of one eye, so the design constraints favor glanceable, contextual information rather than complex interfaces.

This is a fundamentally different design challenge than building for phones or headsets. You are not creating an app that demands attention. You are creating information that sits at the edge of awareness and becomes useful at exactly the right moment. The developers who understand that distinction will build the experiences that make Ray-Ban Display feel essential rather than gimmicky.

Developer Preview Limitations

Meta is being clear that this is a developer preview, not a fully open app ecosystem. Developers can prototype, test, and share experiences, but general publishing through a public storefront is not available yet. The rollout started May 14 and is expanding over the coming weeks, so access is gated rather than immediately universal.

That staged approach makes sense given the form factor. Unlike a phone or headset where a bad app is easy to close, a poorly performing glasses app sits in your field of vision. Meta presumably wants to vet the early experiences and refine the platform guidelines before opening the floodgates. The tradeoff is that the ecosystem will grow slowly at first, but the quality bar should be higher as a result.

Why This Matters for the Glasses Race

Meta is opening its glasses platform to developers at the same moment Google is building the Android XR ecosystem with partners like XREAL and Samsung. The timing is not coincidental. The smart glasses category is entering a phase where the winner will be determined not by hardware specs but by which platform has the better app ecosystem. Meta has over two million Ray-Ban units in the market. If even a fraction of those users start accessing third-party apps through the display, Meta has a developer audience that Google's partners cannot match yet.

The web development path is particularly strategic. By letting anyone with HTML and JavaScript skills build for Ray-Ban Display, Meta is casting the widest possible net for developer talent. Native mobile development requires platform-specific expertise. Web development is a skill that millions of developers already have. That difference in addressable developer talent could determine which glasses platform gets to a critical mass of useful apps first.

The Meta Wearables Device Access Toolkit is available now in developer preview. Documentation and getting-started guides are published on the Meta for Developers portal.