CLAD Summer Hackathon — Week 1: Continuity, Version Control for the Real World

Continuity is basically physical version control for real-world setups. You save a workspace as a “Take,” then later compare the current scene against it to see what moved, rotated, or went missing, and restore the setup using spatial 3D ghosts.

Think film sets, creator studios, YouTube or product-shoot setups, retail displays, gallery installations, or any workspace that needs to be rebuilt exactly the way it was.

Under the hood, WorldQuery establishes the physical workspace, Gemini helps understand the objects in the scene, and rigid registration brings the saved state back into the correct real-world position. For this video I’m using a deterministic demo mode with prebuilt 3D props so I can reliably film the full workflow without hardware/environment variability — those objects are just demo stand-ins; the actual system is designed to observe and reconcile real physical objects in your environment.

u/kamilgibibisey — 3 days ago

Finally got to test my July Spectacles entry, SunSeat, properly at the beach ☀️

I shared an earlier version of SunSeat here a little while ago, but I didn’t really have a decent place — or video — to show how it actually works.

I built it earlier this summer as my July Spectacles entry, and while I was at the beach this weekend I finally got to use it in exactly the kind of situation I designed it for :)

The idea is simple: SunSeat lets you preview how sunlight and shade will shift around a spot before you settle there.

You calibrate the ground, align the sun’s real-world position, and the Lens uses your location, time and orientation to calculate and anchor the sun’s path around you.

Then you can look at a shade source — an umbrella, wall or tree — and move time forward to see how the shade will shift. You can scrub through time manually or use voice commands, with simple verdicts like SHADE HOLDS or SUN HITS IN 22 MIN.

In this video, I checked where the umbrella shade would be a couple of hours later and moved my lounger accordingly.

It’s not only about beach chairs either — the same idea could be useful for choosing a café table, setting up a picnic, planning an outdoor shoot, or simply knowing where the light is going to be later.

Finally managed to shoot it somewhere that makes sense. Would love to know what you think.

See earlier post here: https://www.reddit.com/r/Spectacles/comments/1vc0n40/sunseat\_preview\_the\_shade\_before\_you\_sit/

u/kamilgibibisey — 10 days ago

SunSeat - Preview the Shade Before You Sit ☀️

I built SunSeat back in June for the June Spectacles challenge for this summer, but didn’t submit it at the time. I changed my mind at the last minute, so this is not a polished demo, I will post one this weekend — but the Lens is working.

SunSeat is a spatial sun and shade forecasting Lens built for Spectacles.

First, you calibrate the Lens to your surroundings and the real position of the sun. Then you look at the wall, umbrella, tree or structure you want to use as a shade source. SunSeat anchors that source in the physical space and visualizes where its shadow falls.

From there, you can move time forward (or backwards) manually or use voice commands like “Show me one hour from now.” The sun moves along its path, the projected shade shifts across the environment, and SunSeat previews how exposure around the selected spot will change over time.

It also turns that forecast into simple, glanceable verdicts such as:

SHADE HOLDS
SUN HITS IN 22 MIN
SHADE STARTS IN 18 MIN

The idea is to help you make a better decision before sitting down at a café, terrace, beach, park or anywhere outdoors:

See one hour ahead before you sit.

Built with 5.15.4

u/kamilgibibisey — 20 days ago
▲ 21 r/MetaGlassesforDevs+1 crossposts

Built a tennis scorekeeper + changeover coach

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.

u/kamilgibibisey — 22 days ago

About the potato slide 🥔: A small thought on how Specs were introduced

I’m saying this with a lot of love for Snap and Spectacles. I’ve spent a lot of time building for them, defending the category, and trying to explain why they matter.

But I think something got lost in the conversation around Evan’s talk and the public reaction to Specs.
Most people are not watching this from places like LA or SF, where it feels normal to ride a Waymo to work, or talk about spatial computing and AR every day.

I am almost 43. Most of my friends are around my age or a little older, and many of them still don’t know how to check battery health on their iPhones. They are smart, successful people — they are just not living inside the tech bubble. It also took them months to understand what I actually do for a living, and I think they still believe I “make filters.” 🥲

So when people compare Spectacles to Meta Ray-Ban Display glasses, I understand why. From the outside, the reaction becomes: “These are bigger, heavier, and more expensive. Why would I buy this instead?”

For developers, the difference is obvious. A display is not the same thing as a device that understands space, surfaces, hands, voice, AI, multiplayer interaction, and 3D content in the real world**.**
But that difference is invisible unless it is explained very clearly.

And this is where I think the messaging became difficult. At AWE, it makes sense to speak to developers and explain CLAD, AR, hand tracking, world mapping, and the technical foundation. That is the right audience for those details.

But if the goal is also to introduce Specs to a broader public, especially through a fashion-and-culture campaign featuring names like Kaia Gerber, then the story has to be told somewhere else, in a much simpler way.

Because outside a few tech-heavy circles, most people are still living through phones. Even Gen Z, in most of the world, is not thinking about spatial computing every day.

So if the mainstream reaction is “Why are these glasses so big?” I don’t think that means the product is wrong.

I think it means the category was not explained clearly enough.

People need to see the magic before they can understand the size and the price.

reddit.com
u/kamilgibibisey — 2 months ago

FauxRox: a fake HYROX race for real AR workouts (DEMO)

Hi again everyone,

I built a new Spectacles lens called FauxRox for the May Lenslist challenge, and sorry I couldn't shoot the full demo sooner.

FauxRox is a HYROX-inspired AR fitness race for Spectacles. You run through a dynamic spatial course, cross start and finish gates, complete movement-tracked and distance-tracked workout stations, connect a Bluetooth heart-rate monitor, compare your results on a cloud leaderboard during the race against other racers from around the world, and get short AI coach feedback while you train.

The part I’m most excited about is that it’s built more like a race engine than a workout overlay. There’s a custom "race state machine", dynamic station spawning, camera-based run distance, station gate crossing, burpee rep validation using camera drop/rise/forward movement, hand-tracking zones, finish analytics, PB tracking, and leaderboard panels.

The AI coach is also connected to the race system. You can ask it questions during the workout, but it can also react to race events, heart-rate zones, personal-best pace, form reminders, and the final race summary using Gemini Live voice output.

FauxRox uses BLE heart-rate parsing, Gemini Live, persistent onboarding/profile data, hand/camera/head tracking, and Supabase Snap Cloud for race history, personal bests, splits, HR stats, and leaderboards.

The goal was to make AR fitness feel less like a floating HUD and more like a playable race system running directly on Spectacles.

It’s also an open-source entry, so you can view the repo here: https://github.com/ruyabaraz/FauxRox

PS. The rep counts and distances in the demo are shortened on purpose, but they’re configurable under the Course Manager if you want to tune the race length in the project.

u/kamilgibibisey — 3 months ago

FauxRox: a fake HYROX race for real AR workouts

Hi everyone,

I built a new Spectacles lens called FauxRox for the May Lenslist challenge.

It’s a HYROX-inspired AR fitness race for Spectacles. You run through a dynamic course, cross start and finish gates, complete movement-tracked workout stations, compare your results with other racers around the world via Supabase, connect a Bluetooth heart-rate monitor, and get short AI coach feedback while you train. Each station basically feels like its own mini lens.

Technically, it uses a custom race state machine, dynamic station spawning, ground calibration, camera-based distance tracking, hand-tracking zones, burpee rep validation with camera drop/rise/forward movement, BLE heart-rate parsing, Gemini Live voice coaching, and Supabase Snap Cloud for race history, personal bests, splits, HR stats, and leaderboards.

The goal is to make it feel less like a workout overlay and more like a real AR race system running on Spectacles.

This is just a teaser of the demo. I’ll post the full thing tomorrow.

Ps. Rep counts and distances are very small for demo purposes.

u/kamilgibibisey — 3 months ago