Your Ray-Ban Meta App Development Partner
L+R builds Ray-Ban Meta applications as an early partner on Meta’s Wearables Device Access Toolkit.
Meta opened the toolkit to a small group of studios before general availability, and we helped shape how it works in practice. We build against the real device surface: camera capture, audio in and out, permission flows, and the handoff between glasses and phone.
We build for Ray-Ban Meta Display, Ray-Ban Meta, Oakley Meta, and Meta AI glasses. Engagements start with a scoped prototype on real hardware, so the interaction model is proven on-device before a full build is committed. For the wider category, see our wearable technology practice.
What We Build for Meta Glasses
- Capture flows. Hands-free photo and video, on-device triggers, consent and privacy states.
- Voice and glanceable interactions. Audio-led flows for the camera glasses, and glanceable heads-up moments on Ray-Ban Meta Display.
- Companion app architecture. Pairing, sync, and deciding what belongs on the glasses versus the phone.
- Extending an existing app. Adding a glasses surface to a product you already ship.
- Permission and review readiness. The device-access model and the submission path.
Shipped Work, On Real Hardware
From accessibility tools to guided tours and live displays, our Meta glasses apps are published and public. Everything is designed and tested on the hardware in our own device library, so what you review is what ships.
Common Questions About Ray-Ban Meta App Development
The category, in plain terms.
Four devices, in two kinds. Ray-Ban Meta, Oakley Meta and Meta AI glasses are camera glasses: camera, microphones and speakers, with no screen. Ray-Ban Meta Display adds a small translucent display in the right lens. Meta’s Wearables Device Access Toolkit covers the whole family, and L+R builds for all four.
The glasses handle the moment: capture, a question, a short answer, a glance. The companion app on the phone holds anything a person needs to read at length, review or come back to. Deciding that split is most of the design work, and it is the first thing we prototype.
We were an early partner on Meta’s Wearables Device Access Toolkit, before general availability, and we published our own tooling on top of it. Our Flutter plugin flutter_meta_wearables_dat is open source, so any team can read the code we build with.
When I first experienced the Ray-Ban Meta glasses, it was a clear glimpse into the future of wearable technology. Its a significant advancement, and our team is eager to explore the new opportunities it presents for our clients.”
Director of Engineering • L+R
Building For Ray-Ban Meta, Oakley Meta And Meta AI Glasses
What the camera glasses can do.
The device surface is camera, microphones and speakers, reached through the Wearables Device Access Toolkit. An app can take a photo or a video hands-free, stream what the wearer is looking at, listen to a spoken request, and answer out loud.
In voice and in sound. Audio carries the whole interface on these frames: a spoken prompt, a short answer, a confirmation you can hear. Designing for that rewards short, confident interactions over anything that needs sustained attention.
Building For Ray-Ban Meta Display
What the display changes.
There is a small translucent display in the right lens, so for the first time in this family an app can put something in front of the wearer’s eye. It sits over the real world rather than replacing it, which means the design question is not “what fits on the screen” but “what is worth interrupting the world for”. Glanceable beats detailed, every time.
With the Neural Band, a wrist band that reads the small muscle signals of a pinch or a swipe, alongside voice. It means a person can navigate without raising a phone or talking out loud in a quiet room, which is what makes the display usable in public.
Yes. We built displayglasses.dev, a free browser-based simulator of the display. Load any URL into the simulated heads-up display, adjust its position, size and brightness, swap the background scene, capture or record the result, and preview it on a phone or on the glasses themselves via a QR code. It reproduces the additive waveguide blend over real-world scenes, so you can judge contrast and legibility before writing a line of device code. It is the same tool our own team designs with, and you can try your own idea in it today.
Building from a Flutter App
Building here from a Flutter app means bridging to Meta’s native toolkit on both platforms first, which is work every team has to do before it can do anything interesting. So we did it once and published it: flutter_meta_wearables_dat, an MIT-licensed plugin that handles device registration, camera permissions, live video streaming and raw frame access. It is on pub.dev, it is free, and it is the code we build with.
Want To Know If Your Idea Works On The Glasses? Start With A Prototype On Real Hardware.
Apps We've Built For Meta Glasses
L+R In The Meta Wearables Ecosystem
Choosing A Ray-Ban Meta App Development Partner
How to compare studios in this space.
Hands-on time with the device, and work you can go and check for yourself. L+R was an early partner on Meta’s Wearables Device Access Toolkit, before general availability, and builds across Ray-Ban Meta Display, Ray-Ban Meta, Oakley Meta, and Meta AI glasses. We have also published our work for the platform in the open, which is the part you can verify without taking our word for anything.
We start with a scoped prototype on real hardware. Proving the interaction model on-device first is what keeps a full build from being designed around guesses, and it gives your team something to hold and react to early.
Still a small group, because the platform only recently opened up. The studios worth talking to are the ones with real access to the toolkit and a track record in wearable and spatial product work. L+R helped shape how the toolkit works in practice rather than adopting it after launch, and has published public developer tools for the platform since.
Ask which devices a studio has actually run code on, whether it had toolkit access before general availability, and whether it has built anything for the platform in the open. Those three answers tell you most of what you need to know.
