u/Potential-Noise5819

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/

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.

I'm a developer building for smart glasses, and every morning I'd end up checking a dozen different places to keep up: company newsrooms, a couple of niche blogs, general tech coverage that mentions glasses. There was no single place for the category the way MacRumors covers Apple.

So I made smartglasses.today: a site that updates every hour with news from Meta, Google, Apple, Snap, and the smaller players, plus an events calendar and a developer guide.

Here's what I just realized building it: even the industry's own major players don't agree on the term. Google's own I/O announcement calls their upcoming devices "intelligent eyewear," not "smart glasses" (source: https://blog.google/products-and-platforms/platforms/android/android-xr-io-2026/). Meta says "smart glasses." Some manufacturers use "AI glasses" for the newer, assistant-driven category specifically, to distinguish from older audio or camera-only glasses. Most of the actual hardware makers in this space, Xreal, Rokid, and plenty of others, aren't even US companies, so I'm curious what terms actually get used elsewhere.

What do you call this outside the US, in your own language if it's not English?

FIFA World Cup just kicked off, and instead of dealing with bloated sports apps that blast you with betting odds and spoilers, I decided to build my own companion app overnight using Claude Code.

Standard apps are completely overwhelming when you just want to follow a few specific teams. I wanted something hyper-focused for casual fans, so I built this with a few specific rules:

• Instant Personalization: Once you select your favorite teams, it automatically populates your calendar with all of their specific matches.
• The "Watch" List: If there’s a crucial game between other teams that impacts your group, you can add it to a "watch" list to keep an eye on tournament advancement.
• Lightweight & Language-Ready: It runs on 100% static data and lets you toggle seamlessly between various languages—no heavy APIs or tracking required, and auto-notifications keep you updated on kickoffs.

Right now, I'm just running a couple of test cycles on the web portal to smooth out the UX, but next is to expand this to smart display glasses next.

If you're curious and want to track my other projects, you can find me on Instagram or Threads @ amy.wm.erz

UPDATE: Github repo: https://github.com/amyerz/world-cup

This is my 2nd display webapp since the glasses open to developer. I wanted to bring my existing webapp app, Scenein.app to wearable hardware.

The app pulls shooting locations from the SF Film Department data and matches them with TMDB metadata. When you stand on a specific street corner, it plays hand-curated YouTube clips of the exact movie scenes filmed at that spot.

I used Claude Code on my phone while walking around the city. I was able to live-debug coordinates, tweak the UI  / UX flow right at Golden Gate Bridge, and deploy hotfixes directly from the Mrs. Doubtfire's house the second an issue popped up.

I am expanding the app to to different cities (LA, NY).

Hope you enjoy!

https://meta-wearable.scenein.app/

Hey everyone!

With WWDC kicking off this week, I wanted to share a fun little passion project I’ve been vibe-coding. I wanted a new way to experience Apple's roots while hanging out in Silicon Valley so I built a lightweight web app optimized for the glasses.

Here is what it does:

Pokémon GO" for Apple Fans: It turns Silicon Valley into a giant tech museum. When you arrive at an iconic historical landmark (like the original Infinite Loop campus or Steve Jobs' garage), you can check in to unlock unique digital patches and instantly watch curated history deep-dives right on your glasses.

Keynote Bingo Board: Predictions and rumor mills from the major Apple news sources (MacRumors, 9to5Mac, Macworld, etc.) to generate the cards. Leaderboards track tech publication got their rumors right the earliest.

It’s a total hobby build, free to play, and just meant to be something fun for the community.

Give it a try here: https://apple-50.vercel.app

(Responsive design for both glasses and mobile)

If you're watching the stream or exploring Silicon Valley, let me know what you think!

You can find my other side projects and dev updates on Instagram/ threads @amy.wm.erz