What actually shipped
Meta Ray-Ban Display is a pair of Ray-Bans with a full-colour micro-LED display inside the lens, paired with the Meta Neural Band, a wristband you use to control it. It starts at $799 in the US including the band, launched in the UK at £749, and is also sold in Canada. In the US it is stocked through ordinary retail: Best Buy, LensCrafters, Sunglass Hut, Ray-Ban stores and Meta Lab.
The display-free Ray-Ban Meta line continues alongside it, with newer models starting around $299. Those have cameras, speakers and an assistant, but no screen, which matters a great deal for what you can build.
The part that changed for us, and the reason this is worth your attention rather than a gadget headline, is that Meta opened the platform to third-party developers.
The two ways to build for it
1. Extend an app you already have
The Meta Wearables Device Access Toolkit is a native mobile SDK. You keep your existing iOS or Android app and push a surface onto the glasses display from it, writing Swift on iOS and Kotlin on Android. The display supports text, images, lists, buttons and video playback.
If you already ship a mobile app and the glasses are meant to be a small second screen for it, this is the route. Your business logic, your accounts and your data stay where they already are.
2. Build a Web App that runs on the glasses
The more interesting option for most people: Web Apps written in ordinary HTML, CSS and JavaScript that run on the glasses directly, with no companion mobile app required at all. They get motion and orientation data, the phone’s GPS, input from the Neural Band, and local storage.
If your team can build a web page, your team can build for these glasses. That is a genuinely low barrier, and it is the reason we expect the first wave of useful glasses software to be small, single-purpose tools rather than big applications. Meta’s Wearables Developer Center carries the guides, API references and sample code.
What glasses are good at, and what they are not
This is where most projects go wrong, and it is worth being blunt, because the word “AR” is doing a lot of misleading work in the marketing.
A display in glasses is for glanceable information. A line of text, a direction, a number, a short list, a caption. It is not a window into a 3D world. If you are imagining a virtual object anchored to your desk that you walk around and inspect, that is a Quest headset or phone AR through ARKit, ARCore or WebXR, not these.
- Good fit: a picking or inspection checklist that advances hands-free; live captions or translation during a conversation; turn-by-turn directions for a field engineer; a short prompt at the moment someone needs it.
- Poor fit: anything with real 3D content, room-scale tracking, precise spatial anchors, dense UI, long reading, or a workflow that needs the person to study something on screen.
The other honest constraint is deployment. These are consumer devices sold through consumer shops. There is no fleet-management story comparable to rolling out a set of Quest headsets to a team, and Quest 3 and 3S remain Meta’s business headsets. If your plan involves handing devices to fifty staff and managing them centrally, plan around that gap rather than assuming it away. Our note on Quest for Business ending covers the management side in more detail.
What a sensible first project looks like
The teams getting value from this are not rebuilding their product for glasses. They are picking exactly one moment where a person’s hands are busy and a single piece of information would help, and shipping that.
- One screen, one job. If it needs a second screen, it probably belongs on the phone.
- Design for the Neural Band, not for touch. The input model is a wrist gesture, so the interaction has to be coarse and forgiving. Anything requiring precision will frustrate.
- Assume glances, not sessions. Someone reads this for two seconds while doing something else.
- Keep the phone as the brain. GPS, network and heavy work stay on the phone; the glasses show the outcome.
- Prove the moment first. Build the cheapest possible version, put it on a real person doing the real task, and find out whether the glance actually helped before spending more.
What it costs
A focused single-purpose Web App sits close to our Spark package, which starts at $999, because the scope is genuinely small: one screen, one job, very little content. Extending a production mobile app onto the display with live data and multiple states sits nearer Launch, from $2,999, and scales with how much of your existing system has to be touched.
If you want a number for your own idea before talking to anyone, our cost calculator takes about two minutes and asks for no email. For a proper figure, send us what the glasses need to show and you will have a fixed quote within 48 hours.
Should you do this now or wait?
Honestly: it depends on whether you are selling something or learning something.
If you want a marketing moment, glasses are the most interesting-looking thing in consumer tech right now and a small, genuinely useful demo will get attention that a phone app never would. If you have a real operational problem where hands-free glanceable information saves time, that case stands up on its own and is worth building today. If neither is true, and the plan is to be on the platform because it is new, wait. The SDK will still be there, it will be better documented, and the install base will be larger.
What we would not do is treat this as a replacement for the AR you already had planned. Phone AR reaches billions of devices today. Glasses reach the people who bought a pair. They are different products solving different problems, and the right answer for most businesses this year is still phone-based AR, with a glasses experiment alongside it if there is a genuine hands-free moment to serve.
Common questions
Can you build apps for Meta Ray-Ban Display glasses?
Yes. Meta opened Ray-Ban Display to third-party developers through two routes. The Meta Wearables Device Access Toolkit is a native mobile SDK that lets an existing iOS or Android app extend onto the glasses display, written in Swift or Kotlin. Separately, Web Apps built with ordinary HTML, CSS and JavaScript run directly on the glasses without a companion mobile app at all.
How much do Meta Ray-Ban Display glasses cost?
Meta Ray-Ban Display starts at $799 in the United States, which includes the Meta Neural Band worn on the wrist. It launched in the UK at £749 and is also sold in Canada. The cheaper display-free Ray-Ban Meta range starts around $299. Prices and availability vary by market, so confirm on Meta's own store before budgeting.
Do you need a mobile app to run something on the glasses?
Not any more. A Web App built in HTML, CSS and JavaScript runs on the glasses on its own, with access to motion and orientation data, the phone's GPS, input from the Neural Band and local storage. If you already have a mobile app and want the glasses to become a second screen for it, the native toolkit is the better fit.
Are smart glasses ready for business deployment?
Partly. They are consumer devices sold through consumer retail, so there is no fleet management story comparable to deploying Quest headsets. They work well for glanceable information in front of one person's eyes. For a managed rollout across a team, Quest 3 and 3S remain Meta's business headsets.
Should we build for glasses or for a Quest headset?
Ask what the user's hands and attention are doing. If someone needs a small piece of information while working, walking or talking to a customer, glasses fit. If they need to see and manipulate something in 3D, or be trained in a simulated environment, that is a headset job. The display in glasses is for glanceable text and simple graphics, not for immersive 3D.
What does it cost to build a smart glasses app?
A focused single-purpose Web App is close to our Spark package, which starts at $999, because the scope is deliberately small: one screen, one job, very little content. Extending an existing production mobile app onto the display, with real data and multiple states, sits nearer Launch at $2,999 and upward. You will get a fixed quote within 48 hours of us seeing what the glasses need to show.
Related reading
Got a hands-free moment worth building? 🕶️
Tell us the task and who is doing it. We will tell you honestly whether it belongs on glasses, on a headset, or on the phone they already own — and give you a fixed quote within 48 hours.