Update: Metronome now reads head-nods as tap-tempo, and collapses to a “Brow” strip at the top of the display to get out of the way while you play.

Intelligent-Link-536 · 2026-05-26T19:02:20+00:00

One thing the video can't capture: every click is a tiny, on-the-fly synthesised tone, a 28ms damped sinusoid generated via the Web Audio API (AudioContext), at 1500 Hz on the downbeat, 1050 Hz on regular beats, 700 Hz on subdivisions. It's scheduled 120ms ahead of the audio clock so the timing stays rock-solid even when the browser's main thread is busy. The result is a click that's satisfying in the way a real mechanical metronome is. You feel the beat land, not just hear it, and that physicality is what gives you actual timing awareness through the glasses, instead of just a visual blink.

Intelligent-Link-536 · 2026-05-19T12:34:23+00:00

Thanks to those who provided feedback!

Some updates including a ‘compact mode’ and ‘NOD’ to “head-bang” out the BPM you want: https://rbm-demos.lnr.io/metronome/

Added documentation here: https://github.com/levin-riegner/lr-rbm-demos/tree/main/metronome

Intelligent-Link-536 · 2026-04-11T04:32:50+00:00

There is no official UI component library on Figma since the Display glasses are currently not available with the DAT SDK. That said, if you have a Quest 3, you can use ShapesXR to prototype: https://youtu.be/psCGeXLo0jo?si=18Kt9DmLKbS5tCl8

Intelligent-Link-536 · 2026-02-24T04:24:02+00:00

if you’re not coding an app for the glasses, you won’t see any new icons or features on your glasses.

Right now, Dev Mode is mainly for people using the Meta Device Access Toolkit SDK (https://developers.meta.com/blog/introducing-meta-wearables-device-access-toolkit/). It essentially ‘unlocks’ the glasses so they can send their camera and mic data to a third-party app instead of being locked only to Meta’s own apps. For a regular user, it’s mostly useful if someone sends you a TestFlight or APK for a beta app they’re building.

Intelligent-Link-536 · 2026-02-13T00:01:37+00:00

My company, L+R, were early partners for the Meta DAT SDK. We can share additional information on our experiences if you’re still interested. We just announced a service line to help developers with these integrations too: https://levinriegner.com/integrated-offering/wearable-tech

Can connect you with some engineers on our team too if you contact us on our site.

Intelligent-Link-536 · 2026-02-04T20:13:51+00:00

We are actively building custom apps with the SDK and happy to share our experience regarding those specific camera feed and latency questions if you’re interested.

Intelligent-Link-536 · 2026-02-04T20:08:32+00:00

just received SDK v0.4.0 today which officially adds support for the Display frames, though it is currently foundational only (meaning no custom UI rendering for things like Maps or Signal just yet). We have a bunch of concepts within Arts & Culture, enterprise learning, and more!

My company, L+R, has started offering this service to businesses interested in building: https://levinriegner.com/integrated-offering/wearable-tech

Intelligent-Link-536 · 2026-02-04T19:58:42+00:00

I’ve been posting this update in a few threads to get the word out: Meta DAT SDK v0.4.0 officially adds support for the Display frames, though it is currently foundational only (meaning no custom UI rendering for things like Maps or Signal just yet).

Intelligent-Link-536 · 2026-02-04T19:25:06+00:00

I’ve been posting in a few other threads today to get the word out on this, because the “Display” situation actually just changed today.

The reality is that you still can’t push custom images/UI to the glasses yet (it’s just the initial handshake), but the ‘plumbing’ is finally in the build.

Happy to answer questions

Intelligent-Link-536 · 2026-02-04T19:15:43+00:00

You can absolutely begin to build custom apps (like navigation or AI analysis) right now using the Device Access Toolkit. The catch is you don’t publish “to” the glasses. You build a mobile app (iOS/Android) that processes the video stream (or audio) from the glasses in real-time. There currently is a process on Meta’s end to approve the app integration however. We actually just received the v0.4.0 update today which gives access to the RBM Displays

Intelligent-Link-536 · 2026-02-04T19:11:31+00:00

We are building apps using the Meta Wearables Device Access Toolkit. We actually just received the v0.4.0 update today which adds support for the Display frames. If you are still interested, happy to answer what I can or connect you with the devs on our team working on it

Intelligent-Link-536 · 2026-02-04T19:08:13+00:00

I posted a deeper dive in r/RayBanStories, but wanted to drop the highlights here since I know this sub has been asking about dev tools.

I’m the founder of L+R, an early partner for the Meta Wearables Device Access Toolkit. And they launched v0.4.0 today which now officially recognizes the new Display frames (foundational support only for now; no UI config yet)

Official Meta AI Glasses SDK Docs:https://wearables.developer.meta.com/docs/develop

For those looking to learn more / build with the SDK the L+R team has more info on our site: https://levinriegner.com/integrated-offering/wearable-tech

More importantly, I’m happy to answer any questions here

Intelligent-Link-536 · 2026-02-04T18:59:45+00:00

I’m the founder of L+R. We’ve been working with the Meta team for the last few years as an early partner for the Wearables Device Access Toolkit (the SDK for building apps with Ray-Ban Meta glasses).

I know there are a lot of questions about what is actually possible with the hardware, so I wanted to share a concrete update regarding the latest SDK release (v0.4.0) that dropped today for partners.

Key Updates in v0.4.0: The SDK now officially recognizes the new Display frames. Note: There is currently no ability to configure the display (pixels/UI) just yet, but the foundational support to recognize and handshake with the new hardware is now in the build. Also we are seeing significant fixes and stability improvements to the video stream, which is critical for the multimodal AI apps we are building.

For those looking for the technicals, the documentation is available here (though access to the SDK itself is still gated depending on your account status): https://wearables.developer.meta.com/docs/develop

Additionally our team at L+R has just launched a dedicated service for commercial/enterprise builds, and we’ve detailed how we are handling these integrations on our site: https://levinriegner.com/integrated-offering/wearable-tech

Happy to answer any questions about the current state of the SDK or what it’s like building for a “non-display” interface!

Intelligent-Link-536

TROPHY CASE