We build apps for Meta smart glasses.

The two ways to build, and how we pick

Meta gives you two separate paths. They are not competing options, they solve different problems. Picking the wrong one costs you a rebuild, so this is the first thing we settle.

How an engagement runs

1. 1

   Fit and path

   We decide whether this is a Device Access Toolkit build or a Web App, and we say plainly if it should not be a glasses product at all. That answer is worth more than a proposal.

2. 2

   Account and access

   Meta Managed Account, your organization, Developer Mode on the hardware, project registration, and the permissions your build needs. This is fiddly and we do it for you.

3. 3

   Prototype the hard part

   We build the riskiest interaction first and put it on real glasses. Not a slide deck. The Mock Device Kit lets us start before hardware arrives, and it does not simulate the display, so real hardware is the checkpoint.

4. 4

   Build and test

   Full build, then out to your testers through release channels or a shared Web App URL, with real people wearing real glasses.

5. 5

   Ready for launch day

   Publishing is not open yet. We leave you with a build, a repo, and docs that are ready to submit the day it is, not a prototype you have to rewrite.

Meta Wearables questions, answered

Can you build an app for the Meta Ray-Ban Display?

Yes. There are two ways and we build both. A Web App runs on the display itself in HTML, CSS, and JavaScript with no companion app. The Device Access Toolkit extends an iOS or Android app you already have onto the display. Which one is right depends on whether you are adding to an existing product or starting something new.

Do I need a companion mobile app?

Not for a Web App. It runs on the glasses on its own. You do need one for the Device Access Toolkit, because that path is built around extending a mobile app you already have.

Can I publish to an app store?

Not yet. Meta wearables development is in Developer Preview and general publishing is not open. You can share with a limited set of testers today. We build so your product is submission-ready the day the store opens.

Which glasses does the toolkit support?

Ray-Ban Meta Gen 1 and Gen 2, Meta Ray-Ban Display, Oakley Meta HSTN, and Oakley Meta Vanguard. Camera access spans the line. The in-lens display and Neural Band input are specific to Ray-Ban Display.

What can the app actually access on the glasses?

Through the Device Access Toolkit: the camera for point-of-view video streaming and photo capture, the microphone, and the speaker. Through Web Apps: Neural Band gesture input, motion and orientation data, the phone's GPS, and local storage.

Can you start before we have hardware?

Yes. Meta ships a Mock Device Kit that lets us build and test without glasses. It does not simulate the display, so we plan for real hardware before anything display-facing is called done.

How do users control the app without a touchscreen?

With the Neural Band, a wristband that reads muscle signals in the forearm. Swipes move you around, an index-finger pinch confirms, and a middle-finger pinch cancels. It is a small vocabulary, so the interaction design has to be built for it from the start.

How long does a build take?

A working prototype on real hardware usually takes 3 to 4 weeks. A full build is typically 8 to 12 weeks depending on scope. Because the platform is young, we front-load the risky parts so surprises land early.

Will we own the code?

Completely. You get the repo, the docs, and a clean handoff, same as every Foundri build.

Should we build for smart glasses at all?

Often the honest answer is not yet, or not this idea. A display in the corner of one eye and three gestures is a narrow target. We will tell you if your idea is really a phone app. That conversation is free and it saves real money.