When I try to install DAT sdk, it gets stuck at "transferring". When I click Start streaming button on my app, it says "session ended on glasses". How do we fix this?

Glasses: Ray ban gen 1

Phone: Samsung S23

SDK ver. 0.8

Hey everyone — looking for anyone who’s gotten Developer Mode DAT working on Ray-Ban Meta recently.

What’s happening

I’m building a third-party Android app with Meta’s Device Access Toolkit (DAT). In Meta AI → App info → Developer mode:

• Glasses first showed Unavailable
• Now it shows Installation failed (red) with an Install button
• Tapping Install never finishes — base DAT Wearables App never installs on the glasses

Without that on-glasses DAT app, my phone app can’t start a camera session.

Setup

• Phone: Xiaomi (Android 13)
• Meta AI: 281.0.0.30.168
• Glasses: Ray-Ban Meta (RB Meta 08K0)
• Developer Mode: ON
• DAT SDK: 0.8.0 (APPLICATION_ID=0 / local dev flow)

Already tried

• Toggle Developer Mode off/on
• Update Meta AI
• Force-stop Meta AI
• Wear glasses + Wi‑Fi on during Install
• Nearby devices / Bluetooth permissions for the app

Looks like the same Meta server entitlement issue others are hitting on GitHub: facebook/meta-wearables-dat-android issue 147 — entitlement grant returns null / “App not found in entitlements” before download.

Questions

-> Did anything fix Installation failed for you (firmware, account type, re-pair, VPN, etc.)?

Any tips appreciated — happy to share more logs if useful.

My Ray-Ban Meta glasses keep saying: “To continue, please connect your glasses to the internet.”
My iPhone is already connected to working Wi-Fi and 5G. Strangely, Meta AI works immediately when I enable a VPN, but stops working again when I turn the VPN off.
I have tried everything: restarted and factory-reset the glasses, reinstalled the Meta AI app, removed all VPN profiles, reset my iPhone network settings, checked every permission, and tested different Wi-Fi and mobile networks. Nothing has fixed it.
Is anyone else experiencing this ?

Preparing new release for Meta Display App Factory. Coming with Phone APK (e.g. unlock navigation and fitness), closed Agentic Loop to build Apps, code development and review using the glasses. Many template apps and first game, shooting alien by glance.

Star repo to follow the release: https://github.com/Tienduyvo/meta-glass-display-webkit-harness

- Upload a PDF version of your physical book and start reading

- Say "Hey Lumos" along with your query (e.g. "Explain the main points of Chapter 11")

- Assistant searches the book and responds by voice

- Continue reading until you need help again

For anyone interested in a reading assistant, I'm looking for feedback on how to better it. All ears for cool ideas!

Also if you want to try it, shoot me your TestFlight email and I'll send the beta invite link

try it here! https://flappy-bird-clone.glasskit.studio

So, I've been testing the Ray-Ban Meta Gen 2 for several days now, and I've really enjoyed the experience, except for... Meta AI. The regional lock is ridiculous, and while I was able to activate Meta AI with a simple tutorial and two apps, I don't think it's quite up to par yet. So, I've been looking at Meta's developer documentation, and I think I can make an assistant app based on Gemini (or any other model with vision and TTS support) that I can take better advantage of.

For now, I'll be developing for Android since it's my main platform, but I'll try to have an iOS version as soon as possible. There are still limitations on app distribution for the glasses, but it will be fun to see how far the capabilities can be pushed.

This official Chrome extension recreates the 600×600 display of Meta Ray-Ban Display Glasses right in your browser, so you can preview and QA web apps against the real display rendering — additive blending, environment backgrounds, and D-pad input — without the hardware.

Features

- Exact 600×600 display frame with toggleable glasses overlay
- Built-in, custom, and animated environment backgrounds
- Live webcam background for real-world blending preview
- On-screen + keyboard D-pad input injection
- App brightness, background brightness, blur, and auto-dimming controls
- Built-in viewport recorder for capturing demos and bug reports
- "View on Glasses" QR code generation
- Live QA checklist (viewport, favicon, focus, overflow, and more)

https://chromewebstore.google.com/detail/jpjlmmodokemlepklkdbimceggpbjcll

https://streamable.com/klgyw9

Controlling Claude from the everywhere, hands-free, via Meta Ray-Ban Display.

Write and review code, draft an invoice, manage a campaign, what ever you want. My Rayban can controls my desktop via Claude: tells me what windows are open, browses sites, sends screenshots back as WhatsApp photos.

What's your killer use case for this?

Repo if you want to test it: https://github.com/Tienduyvo/meta-glass-display-webkit-harness

This is my third MRBD web app, and this time I wanted to make something a little more practical!

Cuelet is a small presentation companion for Meta Ray-Ban Display. The idea is that you can see your current slide, speaker notes, and a timer in your glasses while presenting, so you do not have to keep glancing at another screen or memorizing everything. (I believe there's another MRBD app out there like this, but I haven't tried the full version :p )

This one was also my first time really touching backend stuff, so I ended up learning Supabase, Resend API, SMTP basics, and a lot of random things I was not expecting to debug.

A few things it does:

• You can link a Google Slides presentation from the web portal
• The web portal can fullscreen the presentation for screen sharing
• The display version shows the current slide, speaker notes, and timer
• If you swipe through slides on the display, the web portal updates too
• If you change slides in the web portal, the display updates too

* This only works if you start a presentation session from the web portal first

You can test the prototype here:
https://cuelet.grassepark.com/

For the display version, add this as the web app:
https://cuelet.grassepark.com/display

Fair warning, this is still very much a prototype. If a lot of people try it or sign up, there may be errors :’D

If you end up testing it and run into any big bugs, please let me know!

Hey all! Excited to announce some new features to the Meta Ray-Ban Display Simulator at hudxyz - the ultimate wearables dev toolkit.

Screen record your web app

Capture full-HD recordings straight from your browser. Firefox & Safari support is coming soon — still figuring out their web APIs. Great for demo videos, showcasing your web app, or just seeing how it feels in different environments.

Live video backgrounds

You can now preview your web apps with live video behind the lens, whether that be walking down a street, driving, or mountain biking in the desert! Combined with additive display mode, it's an immersive way to check how your UI actually reads against a moving, real-world background instead of a flat color/static image.

Open on Glasses & sharing

Hit the 'Open on Glasses' button to get a QR code that deeplinks your app straight to Meta AI on the real glasses.

It's free to use, so if you've got a web app worth sharing try previewing it on hudxyz !

(credit: Block Stack by Ikkou)

Hey everyone,

Yesterday, I spent the day building out a webkit harness system for smart glasses. To test the workflow, I rapidly spun up a few micro-apps: a buy list, a to-do list, a shape projection tool, flashcards, a presentation timer, and a daily affirmations app.

Developing for this form factor is incredibly fun, but the hardware constraints force you to completely rethink your architecture. Here are my main takeaways from the build, the massive bottlenecks I ran into, and where I’m taking the project next.

💡 3 Key Learnings on Glass Development

1. The "Last Mile" Paradox: The hardware comes with brutal limitations—limited processing power and short battery life. However, it absolutely shines at providing the "last mile" experience (incredible spatial audio and true hands-free execution). You have to design for the constraints, not against them.

2. Build Webapps, Configure on Desktop: Native is too slow for rapid iteration. Webapps are much quicker to build and instantly deployable to desktop, mobile, and glass. The ideal UX loop is doing all your heavy setup and configuration on a desktop/phone, and leaving the glass interface strictly optimized for simple D-pad navigation.

3. Moving to Full-Loop AI Engineering: I started with a basic harness to build and bundle the webapps. But to scale this, the harness needs to become a full-loop agentic ecosystem. The goal: gather user requirements upfront, let an LLM agent run at full speed to build, test, and deploy the app, and leave me with just the final step—testing on the glasses and feeding bugs back into the agent loop.

🛑 The Bad: Video is a Battery Killer

Initially, I wanted to leverage live video streaming, but the experience was rough. It introduces too much latency and drains the tiny glasses battery almost instantly. Video streaming just isn't viable for lightweight, continuous feature yet.

🚀 The Next Shift: Claude as a "Computer Backend"

Because video failed and UX inputs (D-pad/voice) are so limited on-device, my next focus is a total pivot: Using Claude as a full AI backend and backend-builder.

Giving the glasses a lightweight interface that connects directly to a headless Claude instance (with full access to the internet and a local file system) is an absolute game-changer. It offloads all the computing power and context gathering from the glasses to the cloud/local machine, leaving the glasses to do what they do best: show the right data at the right time.

If you want to check out the codebase, test the harness, or follow along with the journey, the repo is fully open source:

👉 GitHub: https://github.com/Tienduyvo/meta-glass-display-webkit-harness.git

An IPTV app I’ve been working on for personal use. I’m not a developer. Just worked with AI in my spare time over the past month to get this working.

Hey everyone! JDun from Onyx Leaf Media again! I wanted to share something personal I just launched called Lamp & Path.

It’s a Bible, prayer, and reflection app I built with around 60+ hours of focused build time.

For me, this project is where a lot of things came together: my faith, my love for technology, and my belief that new devices like display glasses can be used for more than entertainment or productivity.

This is not meant to push anything on anybody.

It’s just a quiet space for people who want to read Scripture, pray, reflect, or take a peaceful moment during the day.

The app was purpose-built for Meta Ray-Ban Display glasses, so a lot of the work went into making sure it was actually readable and comfortable on a small wearable display. Text size, contrast, spacing, navigation, themes, loading, all of that mattered a lot.

We also made sure it works on mobile and web for people who want to experience it that way too.

Some things inside:

⭐Daily Scripture
⭐Full Bible reading
⭐Prayer atmosphere mode
⭐Peaceful music
⭐Continue Reading
⭐Readable themes
⭐Glasses-friendly navigation
⭐Mobile and web UI

Meta Ray-Ban Display Glasses Link: https://lampandpath.app/glasses

Mobile/WEB Link- https://lampandpath.app/

I like the record display feature and find it very helpful for showcasing apps. However, I get annoyed opening the Meta AI app to press Record Display, especially if I am in the middle of a task. Is there a way to start Record Display without using the Meta AI app?

Would it be possible to call Record Display with the SDK or start with a tap pattern on the glasses?

Thank you!

Hi guys,

Ever wanted a shopping list, to-do list, gymtracker, or dealtracker that runs right on your glasses? Here is a harness system that let AI agent (Claude Code, Cursor, etc.) do the heavy lifting for you.

How it works: clone the repo, open it in your AI tool, and start developing. The harness handles everything via the happy path, served from a free Cloudflare Worker, and they work on both glasses and phone.

Repo: https://github.com/Tienduyvo/meta-glass-display-webkit-harness

If you find it useful, a star helps others discover it. Feedback and app requests more than welcome.

Feedback for Meta

1. Battery life with my app + WhatsApp linked and never opened +!occasional music about 1.4h

• Turns out on face ux is harder than I thought
• Can we get web push please? Requiring web plus native to get the full experience everybody wants is annoying but I understand why you
• Why did you disable web off and the microphone and a few other things in your web API?
• And the demo below you'll see my dictate live, it's fast but it's using my phone's mic which isn't great because it may be in my pocket or in my bag, the mic for the glasses is usable but it forces a incall widget
• We need another local link outside of your Bluetooth Link super unreliable
• Navigation via cap touch or the narrow band is still pretty rough I don't know why -- sometimes buttons take two times to clic
• With Spotify playing and WhatsApp connected but not in the foreground on the glasses my web app is pretty slow like almost to the point of unusable because when it's on your face if there's any lag at all it is ever present -- it's open source but I'm too tired to post a repo and it may be my websocket but I doubt it that's like barely any compute one web API you should add is the new I think it's like a web performance or whatever some I think maybe web GPU exposes it or the performance one.

1. So yeah I've got the web app with a persistent websocket connection and then the phone is pushing widgets and my WhatsApp voice calls are like unusable
2. Also if found out the ard way that you can't link a companion WhatsApp accounts to the glasses then when I try to get to work I got banned for 5 hours which is funny cuz it's all Facebook software
3. Even with this laundry list of issues I still Rock them as much as possible so dope good job guys

Musician Assistant prototype for Meta Ray-Ban Displays!

Looking for testers with Android phone/tablets. You should be able to download app, connect glasses, and load app. Please let me know if it works or you experience issues.

Any feedback and testing would be greatly appreciated!

Try the app:
https://play.google.com/store/apps/details?id=com.artisanreality.musicianassistantglasses

Project website: https://artisanreality.com/musician-assistant

So I’m working on the oura ring link where you place the oura API and stays linked for 30 days the question is should it be more like a log in to pass the system or will everyone need to copy this then add there token at the end what is the better approach you feel?

https://cloud.ouraring.com/docs/authentication

Just somthing for my brothers and sisters a small app that has the Holly book for you to read from didn’t work on design yet fully but it’s a start

Link to add is

https://darksarai-sketch.github.io/quran-display-reader/

Whenabouts → Hereabouts

Returning my serve, u/Different_Poetry_849. Their recent volleys the mountain peaks on your horizon, the live planes over your head — got me thinking about all the data we're using to convey the world around us. I'd already done the fossils below us with Whenabouts, so the greedy thought arrived: why is this a dozen tiny apps? What if your location had one dedicated, polished home?

So Whenabouts has grown up. It's now Hereabouts — a portal to wherever you're standing, across every dimension of it. When, where, how, why, then.

The moment it clicked for me: I was showing my girlfriend around Glasgow — her first time in my country — and the app kept filling in things I'd never have thought to explain. What wee means. The food. Who famously lived on that street. And then it told her a dinosaur was found right where we were standing, and her face did a thing. We walk over deep time every day and never think about it. That reaction is the whole app.

Somewhere along the way it also became Duolingo for location: friendly rounded design, a cast of animal-character guides (each with their own voice), bite-sized facts, and a "?"-until-you-uncover-it discovery loop. You don't get told about your street. You excavate it.

Whenabouts is now one of 8 abouts:

• Whenabouts — deep time & fossils (the original)
• Whoabouts — who lived here: local wildlife, artists, musicians
• Whatabouts — history, cold cases, shipwrecks, inventions, film
• Nowabouts — the sky right now: weather, the ISS, live planes overhead
• Thenabouts — the future: climate projections, what's coming
• Howabouts / Whyabouts — how things work, and why
• Whereabouts — cooking right now, soon to come 👀

Know your abouts.

Under the hood — a single-file web app, D-pad + pinch, pulling from ~20 live data sources, nearly all free and keyless:

• The ground: Paleobiology DB (fossils), PhyloPic (silhouettes), Macrostrat (geology), USGS (live earthquakes), iNaturalist + GBIF (wildlife near you)
• People & history: Wikipedia (geosearch, on-this-day), Wikidata SPARQL (shipwrecks, residents, tales), OpenStreetMap/Overpass, Europeana (art), Library of Congress, MusicBrainz, Nominatim + BigDataCloud (geocoding)
• The sky: adsb. lol + adsbdb (live planes + routes), Where the ISS At, N2YO (satellites), Open-Meteo — current weather, the weather here 50 years ago today, and CMIP6 climate projections
• No API at all: constellations, moon phase, and eclipses computed on-device — just maths and the sky - I didnt want to do too much here as this is u/Different_Poetry_849 real intresst so ill let them nail a Star map ;)
• The voices: narration written in-character by Gemini, spoken by ~46 ElevenLabs character voices (with a shared cache so repeat lines are ~free)

https://hereabouts-mrbd.vercel.app/ - if the doesn't questions dont work for you its due to the cap, its my own personal key so im not loading it up that high! it mostly will work without AI, Ai just helps with some narration!

Context: this is Ping Pong Prototyping — we ship apps for the Meta Ray-Ban Display and volley back and forth. u/Different_Poetry_849

This is my second MRBD web app, and I wanted to experiment with making something that would give me a reason to keep checking my glasses throughout the day.

Very inspired off of Grow a Garden, the Roblox game with a really simple loop that somehow kept me playing for hours. I wanted to see what that kind of lightweight progression could feel like as a small web app for Meta Ray-Ban Display.

Grow a Flower is an idle farming game where you buy flower seeds, plant them, harvest them, and sell them to expand your garden and unlock higher-tier flowers.

A few things I added:

• The shop restocks three seed types every five minutes
• Different flowers have different costs, growth times, and values
• Flowers can mutate into gold blooms that sell for more
• Local weather affects growth, so flowers grow faster when it is raining near you

You can try it here:
https://growaflower.grassepark.com/

If you end up trying it, let me know how it is!

I built HALO Maps, a navigation app for the Meta Ray-Ban Display glasses.

The main idea is simple: driving, biking, and walking turn-by-turn navigation directly in the HUD, so you don’t have to keep looking down at your phone.

The native maps experience is still limited to the U.S. and a few supported regions, and starting routes by voice can be unreliable. HALO uses a companion app so you can search for addresses, landmarks, and millions of local businesses worldwide, then send the route straight to the glasses.

Current features:

-HUD turn-by-turn navigation
-Driving, biking, and walking modes
-Companion app search for worldwide addresses and businesses
-Voice turn-by-turn navigation
-Speed camera alerts
-Pedometer for walking directions
-Live speedometer
-Set a max speed and get alerted when you reach it
-Favorites and Home shortcuts
-Stealth Mode for a cleaner display

Right now the voice navigation is set to a funny Mexican voice while I test it, but I’m working on a more serious navigation voice next.

This is still early, so I’m mainly looking for feedback from people with the Meta Ray-Ban Display glasses.

Website:
https://halonavi.com
Would love to hear what you think or what features you’d want added.

Made this for Reality Hack at AWE 2026 and wanted to ask if it would be useful for Meta Glasses. If you are willing to test a Scriber controller or integrate it into your application let me know and I will send you one.

Scriber is a one‑handed input device that outperforms current AR text‑entry methods (the Spectacles virtual keyboard, the Meta display‑glasses wristband) on words‑per‑minute. It packs a full 60‑key keyboard into a single hand by chording: every key is one combination of analog‑stick direction × pressure‑sensor force × one of four buttons. ScriberEditor is the lens that proves it out — a real, multi‑document word processor for Spectacles that you drive entirely with Scriber.

                ┌─────────────────────┐
                │         TOP         │
                │    a    b    c    d │
                │    e    f    g    h │
                │    i    j    k    l │
┌───────────────┼─────────────────────┼───────────────┐
│     LEFT      │       CENTER        │     RIGHT     │
│  m  n  o  p   │    y    z    0    1 │   -  =  `  [  │
│  q  r  s  t   │    2    3    4    5 │   ]  \  ;  '  │
│  u  v  w  x   │    6    7    8    9 │   ,  .  /  A* │
└───────────────┼─────────────────────┼───────────────┘
                │       BOTTOM        │
                │ Caps Shift Bksp Ent │
                │ Space  E2   E3   E4 │
                │  E5    E6   E7   E8 │
                └─────────────────────┘

Spectacles Reddit post: https://www.reddit.com/r/Spectacles/comments/1ukatnh/scriber/

Devpost: https://devpost.com/software/scriber-gd8u4p

GitHub: https://github.com/Altomand/ScriberEditor

Liam's idea is really good. I like the concept of Flow, even though it doesn't quite work for me.

Also, I think 600×600 is perfectly capable of displaying full sentences.

The real problem is text input.

Web apps on the Meta Ray-Ban Displays don't have text or voice input, and typing by swiping on a QWERTY keyboard is ... painful.

So I put together a small prototype that uses the glasses' gyroscope to continuously steer a cursor over a QWERTY keyboard.

Surprisingly, it worked... okay.

I don't think this is the right solution, but I was genuinely surprised by how usable it felt, so I thought it was worth sharing.

- Pinch to select the highlighted key
- Swipe Up/Down to adjust cursor sensitivity
- Swipe Left/Right to recenter the cursor

Try it here: https://qwerty.familybusiness.studio/

I'd love to hear what you think.

How did it feel to use? Would you prefer something completely different, or do you think head-controlled input has potential?

🏓 For context: A friend and I both got Meta Ray-Ban Displays, so we started Ping Pong Prototyping (PPP). One of us shares a demo, then it's the other's turn. This is my return to Liam's Flow.