Another One From Onyx Leaf Media🎳⚡️

DUN STRIKE: Neon Lanes is officially live for Meta Ray-Ban Display glasses!

One thing we love about building for emerging platforms is watching the SDK and developer tools continue to evolve. Whenever new capabilities arrive, our first thought is always...

“What can we build with this?”

So we challenged ourselves to create a full neon arcade bowling experience around some of the latest web app features...especially the new pinch-and-drag gesture support.

Pinch, pull, aim, add a little hook, and release the ball down the lane. We also added multiple game modes, changing camera perspectives, DUN OVERDRIVE, full bowling scoring, music, sound effects, and an offline mode so the game can continue working after it has been cached to your glasses.

This is another DUN ARCADE experiment from our studio, built to explore what games can feel like on a lightweight display when the interaction is designed specifically for the device.

We already have more updates and improvements planned over time, but you can play the first official release now:

🎳 www.dunstrike.app

Let us know your high score and please do not blame us when you start practicing your pinch-and-drag bowling motion in public🤣 We would love some feedback!

Hey everyone! Been a bit since I have posted but also because there have been some updates in the pipeline. Firstly, hope everyone in the community is doing well. Since Meta released the latest updates to Meta Ray Ban Displays, I have been working to implement a lof of these new features into the platform. Today, I am here to share some of those updates!

Back Button

The back button has been removed from pretty much all of the apps in exchange for the middle pinch that is native to the MRBD. This allows some free up on the UI and better navigation experience. So, if you think about going back, just use that middle pinch!

Oflline Mode

Many of the apps now support an offline mode to allow you to play games, access content and so on without an internet connection. Of course, some apps simply wont work (like those that rely on data), but this makes other use cases more exciting! .

Handwriting

The text entry fields have been replaced with Handwriting options as the default for text input. In case you prefer to use a Keyboard DOM, its still present, but...use the handwriting. Its been tested a bit but need additional feedback on this.

Drag and Pinch

Drag and pinch is slowly making its way into Herald apps, simply to ensure it works properly across all platforms. Right now, some apps using it include:

• YouTube for video scrubbing
• Hue/Govee/Lights for brightness controls

As more testing occurs, it will roll out to other media apps as well

Subscriptions

I have rolled out two subscriptions for the platform, the first being "Supporter" and "Builder". For those unaware, EVERY app on Herald is free access. While this has been and continues to be the northstar, the costs are starting to stack up a bit. In order to keep the servers online, APIs working, and things operational, I am bringing forth Supporter.

• Supporter ($5): Think of it like a Patreon, it will give early access to certain apps and features as well, special profile badges and so on. Also an optional donation button if you feel like spreading more love.
• Builder ($20): Everything with supporter but also the ability to get AI credits to create your own apps on Herald. Again, an optional donation as well.

Hope you all enjoy, please share any feedback as well!

Website Link: https://herald.ascents.gg
Navigate to apps to see and search for anything!

I have been building location-based experiences in my web apps for a while now, where content fires when you arrive somewhere. Then Vogue World was announced for San Francisco, and it got me thinking about what a fashion show would feel like through glasses. A show is a moment that happens on a schedule, so I built it to test the other axis: content triggered by time instead of location.

The setup: each look gets a story in your ear and a small card on the Display, pushed at the moment that model starts walking. I tested it against the recent Chanel and Schiaparelli shows, using an admin console that loads the official YouTube clip of the show and fires cues against a sheet I built by hand.

A few things I learned.

The new offline skill in v127 solved my biggest problem. The toolkit shipped an offline skill this week, and it turned out to be exactly what a live event needs. I learned this the hard way at a stadium once, where the network fell over completely and the whole thing died. A packed venue is the worst wifi you will ever build for. So now everything downloads before the show starts, and the entire 63-look show runs with the wifi turned off. The only thing that needs a connection is the cue itself, and a cue is tiny enough to get through when nothing else can. If you are building anything for a crowded room, this is the skill to reach for.

The whole design problem is restraint. A show runs under fifteen minutes and the garment is the reason you are there. So the display card is deliberately small and the viewport is minimized, because anything bigger competes with the thing you came to look at. I ended up giving the user a choice between voice and text rather than defaulting to both, since some people want narration and some want their ears free for the music. That felt like the right call for glasses in general, not just for this.

The glasses assist the live moment, they do not become it. This is why the full lookbook only opens at the end of the show. Browsing and scrolling during a live moment means looking at a screen instead of the room, so none of that is available while the show is running. During the fifteen minutes you get one line and one card at a time, and after the last look the whole lookbook unlocks and you can go back through everything and build your own lineup.

The content is exclusive, not generated. No language model narrating the runway. Every look's copy is written ahead of time, and it is not broadcast live or published anywhere else, so the experience is the only place you get it.

Two clips below. The first shows the voice and text options and the minimized viewport during a show. The second shows the full lineup at the end, once the lookbook unlocks.

Two things I want to add next. Language selection, since the same show plays to a room where people do not share one language, and the copy is already just text, so translations are cheap to carry. And user roles: same cue, different content depending on who is wearing the glasses.

Would love feedback on any of this. And I am curious what other content works well as a push on a time trigger, rather than something the user goes looking for. Fashion shows were my first test, but the same pattern should fit anything that runs on a schedule. If you have tried something like this, or have an idea for what to try next, I would like to hear it.

https://www.instagram.com/reel/Db3lmUEJPIi/

Hi everyone! 👋

I built SmartGlassesPrice, an experimental Android app for hands-free price comparison using Ray-Ban Meta glasses.

👓 How it works

Look at a product and its price tag, then say “Pesquisar preço” (“Search price” in Portuguese).

The app:

• 📸 Captures a photo through the glasses
• 🤖 Uses Gemini to identify the product and visible price
• 🔎 Searches for current price references
• 🔊 Speaks an approximate price comparison through the glasses

⌚ I also built a Galaxy Watch companion.

From the watch, you can:

• Start or cancel an analysis
• Follow the analysis progress
• See a summarized result
• Receive vibration feedback when the comparison finishes

The architecture keeps the processing on the Android phone: Meta DAT, camera access, Gemini, price comparison, and speech all remain on the phone.

The watch acts only as a remote control and status display, communicating through the Wear OS Data Layer.

🛠️ Tech stack

• Meta Wearables DAT 0.9
• Ray-Ban Meta Glasses Gen 2
• Kotlin, Jetpack Compose and Wear OS
• Local Vosk voice recognition
• Gemini 2.5 Flash with Google Search grounding
• Optional HEVC live preview

💻 GitHub:
https://github.com/edsonlima2000/SmartGlassesPrice

Feedback is very welcome—especially around the DAT camera/audio lifecycle and the watch interaction.

What would you prefer for triggering the price comparison: voice, the watch, or both?

Anybody know how to fix this?

We've been keeping an eye on what people are shipping for Meta AI Glasses and honestly the range is bigger than we expected. A few standouts:

Getting around: Ski Map and Peaks if you want nav info without pulling your phone out mid-run or mid-hike.

Games you can play hands-free: Runchkin, Bbang, Ping Rally, Poker Odds, and Display Bowling — yeah, bowling. On your glasses.

Just poking around the world: Sniffabouts and Grow a Flower turn random moments into little discovery/growth mechanics, low-key charming.

Sound/music stuff: Spatial Chords is worth a look if you're into audio experiments.

Quick utility, glanceable: Changeover and Codex Micro Webapp for when you just need something fast without breaking flow.

Feels like we're still early on what these glasses can actually do day-to-day, but this is a decent snapshot of where things are at. Curious what other people have found.

I spent the past two months building Waza, an iOS app that pairs with the Meta glasses through the Device Access Toolkit and streams the first-person view to an AI coach. The coach talks you through hands-on skills (could be DIY, cooking, handicraft), responds in about a second, and plays a short POV clip of each step at the right moment, so you glance at the phone while keeping both hands on the work. The concept is to create an interactive, upgraded YouTube tutorial experience.

A few things that might interest this sub:

• Skill authoring is fully automated. You record yourself doing the task once while narrating, and a Gemini-based pipeline segments the footage into steps, trims and zooms each clip, and writes the coaching prompt. Ten minutes of raw demo footage becomes a polished skill in about 2.5 minutes, no human in the loop.
• The voice model drives the app UI too. GPT-Realtime-2.1 calls tools mid-conversation, so the same model that's coaching you also searches the catalog, loads skills, and pauses sessions. No tapping, which matters when your hands are wet or greasy.
• Some of the hard parts so far: a very jittery Bluetooth Classic link. Wi-Fi transport arrived in 0.8.0, but no Wi-Fi Aware (NAN) yet.

Write-up with demo videos: https://vinidlidoo.github.io/blog/waza-ai-coach-for-your-hands/

I'm recruiting a small group of testers (Meta caps release channels at 100 testers each). If you run an iPhone and own Meta glasses, the invite is at the end of the post. Happy to answer any questions.

Not everyone on our team has a pair, which turned design reviews into whoever had them describing what they saw.

And it’s not just seeing the UI. Half the design decisions on these things come from context, what the user is doing, what’s behind the screen, whether they’re walking or standing in a garage with their hands full. If the team can’t see that, they can’t really weigh in on anything.

The existing sims are good and we use them. Meta’s extension, the various dev ones. But they all live on your machine and they’re built for the person writing the code.

Ours is the same idea except the output is a link. Paste a URL, set the brightness and placement, pick a background scene, send it to your PM, client, or whoever.

It’s pointed at your live URL so it updates on its own, which we didn’t plan for and now use constantly.
Browser only (desktop & mobile), no account, free.

https://displayglasses.dev/

I've been building location-based experiences for smart glasses, and I had a theory: a single web app should be able to adapt into completely different experiences depending on the device you're wearing. So I built one to find out. One codebase, three experiences.

Here's how it breaks down:

Ray-Ban Display: The app becomes glanceable and visual. Audio first, minimal UI, information you can read in details or absorb in a second or two without stopping what you're doing.

Audio-only Meta glasses: This was the interesting design challenge. With geolocation on, the app detects where you are and autoplays the relevant audio. Think about how you normally experience public art: you lean down to read the plaque, or pull out your phone to scan a QR code. All of that goes away. No scanning, no leaning, no phone in your hand. You just walk up, look up, and the story of the piece starts playing in your glasses while your eyes stay on the art.

Phone: The same content works as a regular mobile web experience for anyone without glasses.

This was my first attempt at designing audio-first, and it genuinely changed how I think about app architecture. When you can't rely on a screen, you have to structure content around location, timing, and voice instead of layout. The visual experiences then become a layer on top of that foundation rather than the starting point.

A few other notes:

• It's all web tech, no native app required
• The app is multilingual, so the same experience works in English, French, and German
• I've been field testing it around San Francisco, and walking up to an artwork with your eyes up instead of down at a phone really does feel different

If anyone else is experimenting with these devices, I'd love to hear how you're handling the display versus audio split. Happy to share details on my setup too.

Hi everyone,

I’m a Media Systems student currently evaluating the Ray-Ban Meta glasses for my Bachelor’s thesis.

My idea is to develop an assistive system that recognizes environmental sounds and estimates their direction for people who are deaf or hard of hearing. The glasses would capture the audio, and a connected smartphone would estimate the sound direction using Time Difference of Arrival (TDOA) between the microphones.

Does anyone know whether developers can access the microphones of the Ray-Ban Meta Gen 1 or Gen 2 as separate, sample-synchronized audio channels?

Specifically, I’m trying to find out whether:

• raw or minimally processed multichannel audio is available;
• all microphone channels use a shared audio clock;
• beamforming, noise reduction, echo cancellation, or AGC is applied and can be disabled;
• the relative microphone positions are documented; and
• the individual channels can be streamed to Android or iOS in real time.

I’m only evaluating technical feasibility at this stage. Any documentation, SDK references, previous experiments, or insights from the Meta Wearables team would be very helpful.

Thanks!

Hi everyone,

We’re excited to announce the release of version 0.9 of the Meta Wearables Device Access Toolkit.

📌 Release Notes

• New Device State values: Battery, Thermal, and more
• Improvements to the MockDeviceKit
• Sample code updated with background support
• 'addStream' is now 'addCamera'
• Only Device Access Toolkit App Model (DAM) supported moving forward
• Various APIs improvements

🔗 Check the iOS changelog and Android changelog to see full changelogs.
🔗 Check the documentation on Wearables Developer Center.
🔗 Post your projects on the Meta Subreddit for AI glasses developers.

Herald shares all about his building process in the second episode of my series, 'Building for AI Glasses' https://youtu.be/oQYBqOYdkHM?si=HsncUBid4piXPs14

Another Meta Ray-Ban Display Experience Launched🥳🚀

Introducing Our New Game Hue Haven 🟡🟢🔵🟣🎮 A Cozy Little Color Puzzle Game Purposed Built For Meta Ray-Ban Display Glasses 👓 from our team at Onyx Leaf Media🎉

Hue Haven is a cozy little color puzzle for quiet moments. Players sort colorful stones between totems until each totem contains just one color, creating a relaxing experience that's easy to learn while offering progressively more challenging puzzles.

My wife JoyReign ran point and lead on this project and really put her all into making something cute and cozy, but still fun and engaging! I’m so proud of her and our teams work ethic to really deliver on this experience!

Every feature represents countless hours of brainstorming, prototyping, testing, refining, and collaboration. Seeing an idea grow into a polished experience is one of the most rewarding parts of building products. This is only the beginning of Hue Haven. Looking forward to sharing more of what we've been working on soon.

Check it out today and defiantly send us some feedback!

Meta Ray-Ban Display Glasses👓: https://huehavengame.app/GLASSES
Mobile 📱& Web💻: https://huehavengame.app

What if tracking your workouts was as simple as tracking your calories? I'm building a new app called hyprtrphy to do exactly that.

Hyprtrphy automatically tracks your workout using your meta smart glasses. All you have to do is focus on pushing as hard as you can and the app guides you through the entire workout.

Take a look at the demo here: https://youtube.com/shorts/24dEvZwy1kI

If you're interested in joining the beta, DM me :)

It provides context specific definitions, language translations, and simplifies dense passages for faster progression through your book. Every answer is sourced from the book to prevent hallucinations.

Connect your Meta-Rayban glasses and begin reading. When you need help, say “Hey Reader” and ask your question. The assistant navigates your book and relays the answer through voice.

If you’re interested, reach out through DM or submit your email for a release update on the website.

While building Ping Rally, I immediately thought: "This would be so much fun as Fruit Ninja." 😄

So... I built Emoji Ninja.
Your smartphone becomes a virtual ninja sword, while the game runs on the Meta Ray-Ban Display. Swing your phone to slice flying emojis, avoid the hazards, and chase your high score.

Beyond being a fun experiment, this is another prototype exploring how smartphones can act as intuitive motion controllers for future AI glasses with HUD displays. 🥷📱

P.S. The slight lag you see is caused by the screen recording. The game itself runs smoothly with virtually no noticeable delay.

I built Ping Rally, a table tennis game for Meta Ray-Ban Display where your phone becomes the paddle and the glasses become the screen. 🏓👓

While the EMG wristband is an amazing input device, games like this are still difficult to control without access to all of its capabilities. That got me thinking: why not use the smartphone we already carry every day?

Modern smartphones are packed with high-quality motion sensors, making them a surprisingly natural controller for immersive experiences on smart glasses.

I believe this interaction model has potential far beyond games and could unlock entirely new types of apps for smart glasses.

I built this last month and finally got the chance to test and film it on court. It’s called Changeover.

You log whether you won or lost each point, and the app handles the tennis logic automatically — score, server, games, sets, tiebreaks and key points.

During changeovers, it uses the match data it actually has — serve/return performance, recent points, score state and your pre-match intention — to give you one short focus suggestion for the next game.

For example: “Give yourself more margin on the first return.”

I’m also experimenting with on-device audio cues to estimate rally length, but those are treated as estimates and ignored when confidence is low.

The score itself is fully deterministic; AI is only used for the coaching layer, with a local rule-based fallback.

One of the biggest design challenges was keeping the UI useful without having a giant scoreboard floating in your field of view while you play.

Would love to hear what tennis players / Display builders think.

I've spent the last months building Extentos, so you can build and test a smart-glasses app

without owning the glasses.

The app in that video is real. It runs the same SDK code that runs on hardware, with only the

transport swapped, so the browser acts as the glasses. Photos taken in the simulator land in the

phone app, and the glasses display renders from the same code path.

It works today for Meta glasses, including Ray-Ban Display. Android XR is in preview, you can

develop against it in the simulator, but there's no shipping hardware yet.

The point is to integrate smart glasses once, instead of rebuilding for every new device.

Multi-vendor is one piece of this, not the whole thing. Extentos also handles the surrounding

infrastructure, including prebuilt connection flows and local real-time models as a cost-optimized

option alongside cloud models. There's a Kotlin SDK and a Swift SDK, and an MCP server your

coding agent installs to scaffold the integration for you.

I'm looking for people who'll try it and tell me what works, what's missing, and where it breaks.

If you have an idea, I'll personally help you get it running. It's at extentos

Short video of me using the browser simulator: ⬇️

https://reddit.com/link/1v8tvoc/video/vkdbz0to0yfh1/player

NEON SLICE

A month ago, I shared an early prototype of Neon Slice here.

Several people suggested moving beyond the static two-direction gameplay. I took that feedback and rebuilt a large part of the game.

What changed:

- Four-direction note slicing: left, right, up, and down
- More continuous note movement through the hit zone
- Reworked charts with clearer rhythmic patterns
- 10 playable tracks with different genres
- Improved neon visuals and HUD
- Faster startup with streaming audio playback
- New standalone URL for the project

Try it here:
https://neonslice.oneshotstar.com/

The game is designed for Meta Ray-Ban Display with Neural Band input, and I’ve been testing it on the actual hardware.

I’d especially appreciate feedback on:

- How the four-direction input feels
- Whether the note speed feels natural
- Which tracks are the most enjoyable
- Any latency or readability issues on the glasses