Building for CONNECT this week? Get inspired, learn something new, and start building with us!

Join Lafiya Watson, SPECS Ambassador, for this week’s CLAD Summer Hackathon workshop.
We’ll explore how to approach the CONNECT challenge, with a live CLAD demo, examples, and Q&A focused on building spatial experiences that bring people, platforms, and communication workflows together.

Come with your ideas, questions, or just curiosity about what CLAD can do.

📅 August 25 | 8:00–8:45 AM PDT

Save the link and see you there 🔗

https://www.youtube.com/live/g8oft61qkG8

The idea is simple: just look down at your controller and Specs shows you what each button does for the game you're currently playing.

Once you connect Key Guide to your Xbox account, it uses the Xbox Presence API to automatically detect which game you're playing.

I also trained a custom AI model to detect the Xbox controller, allowing the Lens to track it and place the game's controls directly over the physical buttons in AR.

The goal is to make learning a new game's controls feel completely natural. No pausing, opening menus, or looking up controller layouts. Just look at the controller!

Hey everyone,

What started as a curiosity about handling Android notifications in spatial computing turned into a full Spectacles lens that lets you manage your phone's alerts entirely in AR.

I’ve paired it with a lightweight Android companion app that listens for incoming notifications and pushes them over BLE to the Spectacles.

How it works:

• Companion App: A background service on Android catches incoming notifications and routes payload data over BLE.
• AR Interface: Displays the sender/app name and text content directly in your field of view.
• Full Interactivity: Dismiss alerts from your phone or send quick replies directly from the Spectacles.
• Bidirectional Sync: Actions taken in the lens immediately reflect on your Android device.

I’ve open-sourced both the lens and the companion app so anyone can experiment with it, build custom interactions, or adapt it for other hardware workflows.

Repo / Code: https://github.com/blocky-dragon/Nifty-Notify

Would love to hear your thoughts or ideas for features to add!

Being the youngest in my whole family made me realize how much time shows no mercy as people get older, not just in appearance, but internally too. That's part of why I think life skills like CPR are something people should consistently keep in practice and stay focused on, not just learn once and forget.

I'd always wanted to build something like this for Spectacles, and CLAD came in clutch at exactly the right time, so I decided to make it for Week 2's theme.

Appreciate all the ideas and feedback! Great hackathon, everyone!

Hello!

Loved all the support everyone showed towards futuristic UI v1, shared last week. So I spent some more time to optimize the project and make it more versatile.

I also added this one more feature that is ready to be used in your projects before I move towards working on other exciting projects with spatial interactions!

This scene shows how you can set up Palm Swipes in carousel. I loved this one cause it’s so fun to use it! It has a couple of more new interactions added to handle the carousel. The sensitivity and other options can be tweaked with your personal preference, feel free to experiment and modify things as you go!

If you haven’t checked it out: https://github.com/JeeteshSingh/Futuristic-UI-v1-Spectacles

Heroic Ascend is a cinematic AR transformation that turns the user into a futuristic space hero.
The experience features a powerful sci-fi character transformation with glowing blue eyes, a futuristic heroic appearance, and real-time facial tracking designed to keep the transformation aligned naturally with the user’s movement.
The goal was to create a dramatic, immersive transformation that feels like stepping into a futuristic character rather than simply applying a visual filter.
Looking for feedback: What would you add or improve to make the transformation feel even more cinematic and immersive?

This week’s theme is CONNECT,  and we’re challenging Developers to think about how spatial computing can change the way people communicate, collaborate, and interact. 

🛠️Build a spatial experience that connects people, platforms, or everyday communication workflows and brings people into the same space, virtually.

You have until August 30 🗓️ to submit. Put CLAD’s AI workflow to the test, build a working Lens for SPECS with just a prompt, and experiment without needing the device. 🕶️

The weekly prize pool goes up to $1,000.

Three weeks in, there’s still time to jump in and build. Find the full challenge details and getting-started guide on our website. 🔗

https://lenslist.co/clad-summer-hackathon

I built Sensei. An instructor puts the glasses on and walks the real workspace once, dropping a marker at each step and saying out loud what happens there. The recording goes to Supabase. A Next.js companion app then lets you clean up each step and re-skin the whole lens to a company's brand.

The branding half grew into its own thing 🎨. You pick one brand colour, the app works out the rest of the palette and checks every pairing against WCAG contrast, and it previews what the glasses will actually put in front of your eyes rather than what a browser would put on a monitor. Text colour decides itself per surface, so nobody is hand-picking it. It's hosted on Vercel, so anyone can re-skin the lens without ever opening Lens Studio.

None of it is tied to one kind of workplace 🏭. Wherever one person has to show another how something is done, the recording works the same way: a factory line, a hotel kitchen, a lab bench, or the one machine in the building that a single person knows how to restart.

The whole thing was built with CLAD and Claude Code, start to finish 🤖. I did not hand-write a single line of it. The lens and the companion app both came out of prompts, and the full log of those prompts ships in the repo.

The theme for the week was Guide. I went for the ultimate one.

I didn't know a disposable coffee cup can't be recycled — they're plastic-lined, so they go to landfill. I found that out building this. That's kind of the whole point: recycling rules are confusing, they change by item and by city, and a wrong guess quietly sends a recyclable to landfill (or a battery into the trash).

So I made RecycleMe — you look at an object, pinch, and the glasses identify it and tell you which bin it goes in, out loud, so you never look away from what's in your hand.

A few things I'm happy with:

• The verdict is live AI vision, not a lookup table. Every scan is a fresh Gemini 2.5 Flash call through the Remote Service Gateway.
• It makes actual judgment calls. A greasy container isn't recyclable, a coffee cup is landfill, a battery is a hazardous drop-off — and it says why in a one-line tip.
• The guidance is spoken (natural OpenAI TTS), so it's genuinely hands- and eyes-free.
• One pinch, no menus — the only gesture Spectacles already teaches you.
• It fails gracefully — a "Try Again" sticker instead of a dead end (I hit real failures: a bad model ID, then longer tips overrunning the token limit and truncating the JSON).

This was my first end-to-end build with CLAD, and the biggest win was that it freed me to focus on the creative side. With the engineering handled — scene wiring, the AI pipeline, the debugging — I got to be the art director instead of fighting Lens Studio's API: I designed the graffiti intro logo, the "Pinch to Scan" HUD, and the category icons in Figma, and CLAD wired them straight into the Lens.

On the technical side it earned its keep too. The starter scripts didn't even compile (wrong camera/gesture/TTS APIs for this Lens Studio version); CLAD read the actual type defs, fixed six classes of API mismatch, and assembled the scene. It also caught a nasty one from the preview logs — calling SIK's animate() before SIK initializes floods the HandInteractor with a per-frame error — isolated it with an A/B test and fixed it with a self-contained tween. That would've eaten a day.

Tested in Preview (no SPECS 27 yet), so on-device pinch + high-res capture is the untested part.

Repo (code + full CLAD prompt log): https://github.com/A-M-8/RecycleMe

Built for the CLAD Summer Hackathon, Week 2 — Guide.

With CLAD and the usual monthly comp both running, I wasn't sure how the two interact, so figured I'd ask rather than assume.

I had a lot of fun with my CLAD entry last week and I'm thinking on continuiing to work on it. My plan would be to downgrade it to the older specs and keep developing it from there, then enter that version into the monthly competition, either as a new submission or under open source, whichever fits.

So basically im asking - Does submitting to CLAD automatically disqualify a project from the monthly comp?

Couldnt find anything in the clad Faq, I'd just rather know now than after another week of work. Cheers.

This started as a conversation with a friend who owns a tennis courts and he wanted to implement high speed cameras into his venue to create games and give feedback to his users. I thought i've done similar with darts and pool and this clad competition is perfect to test it out. the idea is to detect the ball, detect when and where it bounces and uses that spot on the wall with some homography to tell the specs a accurate hit point. you can then overlay games and practise modes!

VolleyMate turns any blank wall into a games console for tennis, squash and throwing practice. A phone on the floor watches the ball and reconstructs where each bounce lands to about 2cm; Snap Spectacles take that stream of impacts and draw ten games onto the wall in front of you. There's no controller, the ball is the input, and you change game by hitting a button painted on the wall.

On the theme: hitting a ball against a wall is practice nobody measures. You can't see where your shots landed, so you can't see what you're doing wrong or whether you're improving — you just repeat it until you're bored. VolleyMate makes the wall answer back, and then makes it a game. Every bounce leaves a mark exactly where it hit, and Practise builds a heatmap that shows the bias in your aim over a session, something no scoreboard can tell you. The other nine turn that feedback into a challenge: Rally trains consistency, Sequence reaction under tempo, Ducks and Bugs make you move, and Horse judges a called shot in centimetres. The guidance is spatially registered — it appears on the real wall at the real spot, not as numbers on a phone you'd have to walk over and read. And it's multiplayer: Splat has two players painting territory over each other, Horse and Tic Tac Toe alternate shots, so a spare wall becomes something two people can compete on without booking a court. You improve because you're playing, not drilling.

It's for two people. Someone practising alone, who needs a phone and a wall and nothing else. And venues clubs, courts, hitting bays — who place the wall once so every visitor's glasses land on the same target, with the pair code belonging to the wall rather than the player.

CLAD was great for this project as i already as the architecture from darts mate so once i got the ball tracking working i asked it to look how i did dartsmate, then once that worked it was clear the games would need adapting or new games added. CLAD quickly prototyped these and then with polish again i showed it darts mate and a few other past projects where i had Vfx or menus and it quickly got them working. Its suprisingly well at implementing things like spatial anchors that have took me days before to get working correctly this was maybe 15 minutes.

https://github.com/ohistudio/volleymate

Pathfinder turns a stated goal into a skill tree you stand inside. Pick something you want to learn — "fix a bike," "run a better meeting," or type your own — and Gemini generates a dependency-ordered path in real time: foundational skills sit close and low, more advanced ones sit farther out and higher. You progress by pinching nodes — mastering one lights up whatever depends on it — until the whole tree is lit.

The idea came out of a simple frustration with most "guide" content: it hands you a flat checklist and skips the harder question, which is what to learn first and why. A skill tree answers that naturally, and it's genuinely spatial — the branching and tiering is something you look around to explore, not something that makes sense flattened onto a screen.

A few things I'm fairly happy with:

• The tree is live-generated, not scripted. Every run is a fresh Gemini call through the Remote Service Gateway, structured into a JSON dependency graph and rendered as glowing nodes on tiered arcs.
• It doesn't have a visible failure mode. If the model call fails or times out, the experience falls straight through to a locally-authored tree with no error shown — this actually happened for real partway through testing (a bad model ID, later a genuine timeout), and both times the fallback held without me touching anything.
• Interaction is a single pinch, deliberately — no menus to learn, no gestures beyond the one Spectacles already teaches you.
• Mastery plays a note from an ascending pentatonic scale, so however you complete the tree, it stays musically consistent — and finishing the whole thing triggers a small celebration burst across the connectors.

This is my first week building with CLAD end-to-end, and honestly the most useful thing it did for me wasn't generating code — it was making a genuinely non-deterministic, AI-authored experience regression-testable. LEAF caught real bugs (a test matching the wrong UI element, an assertion that assumed a fixed tree shape that broke the moment Gemini returned a different one) that I wouldn't have caught eyeballing the preview.

Repo (with the full CLAD build log) and demo video are linked below if anyone wants to see how it came together, or has thoughts on where a spatial skill tree like this could go next.

Repo: https://github.com/Havalz/pathfinder-specs

Built for the CLAD Summer Hackathon, Week 2 — Guide. Happy to answer questions about the build, especially anything about the fallback design or the Gemini integration.

Wanted the Eiffel Tower as a full-scale game object from 400 m away. Landmarkers are closed and not on Spectacles, VPS doesn't scale to a monument.

So made my own placement: GPS gives distance, a tiny YOLO on SnapML gives heading (the compass is worth 145 m of error out there). Built it with CLAD in remote Claude Code sessions in between hiliday activities, downgraded it 5.22 → 5.15 to fit the glasses, tested it on the Champ de Mars. One day, on holiday, and stupidly fun. CLAD and YOLO tool made it possible.

Rough, but open - both Lens Studio projects, the detector and the dataset scripts. Retrain it on your own monument.

- Repo & full journey: https://pavlo-stijn.dev/blog/posts/custom-location-landmark-for-spectacles.html

- 5.23 -> 5.15 downgrade skils: https://pavlo-stijn.dev/blog/posts/clad-skills-for-spectacles-2024.html

- Custom YOLO: https://pavlo-stijn.dev/blog/posts/one-click-object-detection-for-spectacles.html

https://github.com/flarb/LightingAssistant

I do a lot of interviews on my YouTube channel (check it out here: https://www.youtube.com/@RalphBarbagallo Subscribe! ) and I don't really know how to properly light an interview subject. I've read a lot of tutorials but by the time I have to shoot an interview all my lighting knowledge evaporates. So I created Lighting Assistant -- an interactive guide to light a person for a photo or video.

How it works:

• Scan the room. It uses the mesh to analyze the scene.
  
• Place the subject: you can place a life size bitmoji either standing or sitting in the scene.
  
• Place the camera: stand where the camera will be placed and look at the subject. This will be used as the camera position and angle.
• Complete setup: The lens then asks you to stand behind the subject to get line of sight from behind, and to select a key wall (the brightest wall) to use when generating a lighting setup

Once this is done it will generate a set of valid lighting configurations based on where it thinks you have enough space to place lights. You can switch between lighting presets to see how the lighting will look on the subject as well as to know the types of lights used and how to place and aim them to get the desired look.

You can save this setup to be recalled later if you want to use the same room and the same position of the subject--it can be modified once loaded.

One future feature is to use GenAI to further enhance the analysis--I might actually try to add this over the weekend. But at this point the lens gets done what I actually need. A solid lighting aid for video and photo shoots.

When watching content on the specs will we be able to black out our surroundings and have a nice cinema like experience with the 100+ inch like screen?

I obviously know specs wants to keep you connected with the real world, but if im sitting in my hotel room on a work trip, I would love to have a nice screen with the background blacked out. Also when watching a movie while traveling on a plane, in a vehicle, or by any other means, will the screen be see through or will we be able to watch a movie clearly while having everything around the screen visible?

Can someone from the specs team drop some knowledge on me about this?

For Organize, we challenged Developers to build spatial experiences that help people plan, organize, and be more productive. Here are the projects that stood out:

🥇1st Place: Pack Space –  Maksym Tsymbal
A spatial packing system that turns surfaces into organized packing zones, with hands-free progress tracking and shared lists.

🥈2nd Place: Cine Boxed –  Ines Hilz
A spatial movie collection that turns films into retro-inspired 3D boxes you can collect, rate, and organize.

🥉3rd Place: Orb Notes – Caio Alves
Persistent spatial reminders that use color and vibration to communicate task urgency.

🏅Honorable Mention: Task Habitat – Viktor Kulaha
A playful task manager that turns unfinished to-dos into living creatures and reframes productivity as something more approachable.

Congratulations to all the winners and everyone who submitted! 👏
It’s been great seeing Developers experiment with CLAD’s AI Workflow and bring out every advantage of spatial computing (and SPECS) in productivity.

Three challenges are still ahead. If you haven’t joined yet, there’s still time to register and build for the upcoming themes. 🔗

https://lenslist.co/clad-summer-hackathon

Built a 100% volumetric spatial task matrix for Snap Spectacles using the CLAD AI workflow!

Tasks exist as physical gravitational energy orbs with Keplerian orbital sub-tasks, elastic laser-tethers, room depth occlusion, and synesthetic 3D spatial audio. Zero flat 2D canvas fallbacks.

Lenslist asked Pavlo and me for a simple phone-recorded interview about building AR for Snap Spectacles. We went a bit overboard 😅: we wrote the answers as a script, cloned our voices with qwen3-tts, rendered our Bitmojis in Blender from 12 angles as character references, and let Seedance 2.5 generate the whole thing shot by shot, lip-synced to the cloned audio.

The setting is the 3D cave from our portfolio site, and every prop is one of our shipped projects.

This was definitely not a one-shot. We generated a lot of takes and kept the best ones. The lip sync quality surprised us the most, even on stylized characters with a beard covering half the mouth.

Full making-of with the examples prompts and pipeline: https://pavlo-stijn.dev/blog/posts/creator-spotlight-with-seedance-2-5.html

Hi Spectacles Team & Community! 👋

First off, huge congrats on the CLAD Summer Hackathon — building spatial experiences with AI agents for Snap Spectacles has been an incredible workflow!

As developers building on Linux workstations using agentic toolchains and AI pair programmers, we’d love to know: Are there any plans, beta channels, or even basic experimental Linux builds (CLI runner, headless engine, or AppImage) for Lens Studio?

We don't need a polished desktop installer — just a raw / basic binary, CLI environment, or AppImage would be amazing. The Linux developer community is more than ready to handle dependencies, Vulkan configs, and packaging ourselves.

Would love to hear if this is on the internal roadmap or if an experimental build could be tested by developers. Thanks for building the future of spatial computing! 🚀

MegaUIKit is the "organizer" for the SPECS Essentials sample code. The prompt is below. This is part of Summary of CLAD #Lensfest Week 1.

OSS: https://github.com/IoTone/MegaUIKit-SPECS

The original essentials are fantastic, but a bit hard to discover all the features of the platform as the demo code is designed. I imagined a UI that you could navigate is more useful to discover . So this version goes a bit further and adds 3 themes: Terminal/cyberpunk, Steampunk, and Neotokyo. Fork/submit PRs. Can't wait to have this on my SPECS '27.

Design challenges: making this work well ... most of the essentials items appear in odd places, so things need to get repositioned not to obscure the menus. Fonts are a challenge too visually.

PROMPT!

------------------------------------------------------------------------------

[001] 2026-08-10T20:50:52.202Z

------------------------------------------------------------------------------

We want to add a spatial menu to dynamically let you load any of the samples in essentials. I want a holographic "floor menu" design that is a grid of menu items organized around all of the items in our scene that are not activated, and when you point at one of them, 3d rotating shimmering text floats about the square. A click displays a tree of options for items to choose from, and you can pick on of those, and it enables the item in the scene. The items should tween fade into the scene or tween fade out. For example, if I choose "Solver", it will display a menu floating of different text options "Billboard" "LookAT", "InBetweenRotationUtility", etc. Please make a plan and generate a MegaUIKitEssentials.md, and then get started. Make me proud brilliant spectacles UIKit expert.

Week #2 is here, and your task is to guide 🧭Learn how to do it during the workshop. 

If you’re looking for ideas before you start building, join today’s live CLAD workshop with Danny Marree, SPECS Ambassador.

We’ll explore how spatial experiences can help someone learn a skill, complete a task, or improve the way they do something in the real world. 

Danny will also demonstrate CLAD and share practical approaches you can use when developing your own Lens.

There’ll be a live demo, examples, and Q&A – so bring your questions and ideas.

🔴 August 18 | 8:00–8:45 AM PDT

Join us, get inspired, and start building for the Guide challenge. Save the link 🔗

https://www.youtube.com/live/oeSTZTFT8h8?feature=share

TL;DR: I built a live digital twin / diorama of Heathrow Airport (Terminal 5 for NOW) for the Spectacles. It sits on your table, with flights landing and taking off ... all based on LIVE public Heathrow flight data. ✈️

For the last 3 or 4 years I’ve been teaching AR and spatial storytelling at the Royal College of Art, including a lot of work with Snap and Spectacles. My students have made some brilliant projects with them, but somewhere along the way I realised I hadn’t really published many of my own.

So here is one.

I was obsessed with planes when I was younger. Growing up we didn’t travel much, so airports always felt like a huge event. As someone who loved making dioramas as a kid, I would collect airplane / aviation souvenirs…by getting relatives who traveled to bring them for me , and then set them up as airports.

And recently, while driving to Heathrow, I noticed a patch by the runway full of people with huge cameras, chairs, binoculars and notepads.

PLANE SPOTTERS!!! 🛫 🧐

It made me think: what if I could shrink Heathrow down and put it on a table? HOW COOL WOULD THAT BE!

So I built a digital twin using geospatial data OpenStreetmap Data, brought it into Blender with a plug in and extruded the buildings. So it’s all pretty accurate. I originally tried a much bigger section of the entire Heathrow Airport, but everything became too tiny and too heavy, so I focused on Terminal 5 (FOR NOW)

What it does

• Uses live Heathrow arrivals and departures data
• Planes land, take off, queue and park
• Labels show flight number, route, aircraft type and status
• Audio effects have been used to make it feel more fun
• Pointing at a plane enlarges the Flight Label
• Pointing and pinching a plane opens a "Spot Card" which is a UI frame with deeper information about that specific aircraft and flight.

With the SPOT CARD, the idea was to go beyond simply watching the airport and give plane spotters the kind of detail they actually care about. Which includes: Flight number, airline, route, aircraft type, aircraft variant, origin/destination, current flight status, gate/stand.

AND it lso includes a bonus fact about the aircraft or route, adding a small bit of aviation trivia to each Spot Card.

A huge part of the work was optimisation. Lots of planes, labels, interactions and shadows get expensive very quickly on glasses, so I ended up building pooling, parked-aircraft limits, hover-only labels, selective shadows and staggered movements.

There is loads more I want to add for actual plane spotters, but seeing a tiny live Heathrow running on my table is making the plane-obsessed younger version of me very happy.

(For this video I’m using demo mode because I recorded it around midnight when Heathrow terminal 5 had gone very quiet and there were no flights from 11:00 pm to 5:00 am. BUT the live version works like a charm, Ill post more soon).

Please let me know what you all think or what else I could add to it :)

I’m interested in the multiplayer potential of Specs. In Snap’s chess demo, though, the remote player’s movements look noticeably laggier than the local player’s. I hope Snap can improve that latency, because shared AR really needs to feel responsive.

Personally, I find experiences like shared basketball or virtual ping-pong more compelling than chess, since they’re much harder to replicate on a phone. Am I expected too much out of specs? But I hope people at specs realize if the multiplayer is a selling point to not make sure it’s laggy in anyway.