Meta is giving developers access to the Ray-Ban Display visual layer just as Google I/O brings Android XR, Gemini and AI glasses back into focus. Smart glasses are moving into more testing times, where hardware, apps, input, privacy and platform support all have to work together.
Meta Opens Up The Display Layer
Meta has opened up the display on its Ray-Ban Display glasses, giving developers two routes into the device.
The first is through the Meta Wearables Device Access Toolkit, which lets iOS and Android developers extend existing mobile apps onto the glasses display. The second is through Web Apps, where developers can build standalone display experiences using HTML, CSS and JavaScript.
Developers can now treat Ray-Ban Display as an app surface, with overlays, status checks, utilities and lightweight controls built for the glasses display.
Meta lists early use cases including information overlays, real-time data displays, micro-apps, utilities, experimental interactions and streaming media. Those categories should work in smart glasses fairly naturally: short, glanceable experiences that can be useful without pulling the user back to a phone.
The Neural Band Solves An Awkward Problem
Meta Neural Band is big for developers.
The band uses surface electromyography, or EMG, to detect subtle finger and hand movements. Ray-Ban Display users can control the glasses without relying entirely on voice, phone screens or taps on the frame.
Voice is still useful, but it fits some settings better than others. People won’t always want to talk to their glasses in an office, on a train, in a warehouse, in a shop or during a meeting. Phone control pulls attention away from the glasses. Frame controls can only carry so much complexity.
Gesture input gives developers a more discreet interaction model. It suits quick decisions, lightweight navigation, status checks and simple controls, which is probably where early display glasses apps will have to earn their place.
Google Has Its Own Glasses Moment Coming
Google I/O runs across 19 and 20 May, with livestreamed keynotes, sessions and developer activity. Android XR will be one of the areas to track, especially after Google’s earlier framing around Gemini, headsets, glasses and partner eyewear.
Google has already described Android XR as a platform for glasses as well as headsets, with Gemini supporting use cases such as live translation, messaging, navigation and visual assistance.
It has also talked about eyewear partnerships with Gentle Monster, Warby Parker and Kering Eyewear, alongside Samsung’s role in extending Android XR beyond headsets and into glasses.
Meta enters this week with hardware in market and a developer preview for the display. Google enters with Android, Gemini, Samsung and eyewear partners. Both are pushing smart glasses toward a more serious app and platform layer.
Smart Glasses Need Jobs, Not Just Cool Frames
Better frames will help the category, as will stronger batteries, clearer displays, prescription options and less awkward social design.
The software layer now needs to catch up.
Smart glasses need useful jobs that fit small moments: checking a status update, following a step, seeing a direction, translating a phrase, confirming a task, getting a visual prompt or controlling media without reaching for a phone. Developers need stable tools, usable input models and enough confidence that the device category will still be around when their work ships.
Enterprise buyers will ask a different set of questions. They’ll want to know how the devices are managed, what data they collect, how privacy is handled, which workflows fit the form factor, how apps are deployed and whether the glasses can survive real working conditions.
Meta’s developer preview gives Ray-Ban Display a wider developer surface. Google’s Android XR push gives I/O a smart-glasses platform angle beyond the keynote demos. The next phase will depend on whether these ecosystems can give users something worth glancing at, controlling quietly and returning to every day.
