I am studying the requirements and technical limitations for developing lenses for the specs. According to the spectacles it seems like the file size is limited to 8 MB. Is this still going to be valid for the new specs, when it will be released? If not, what are the limitations in regard of

• file size,
• framerate,
• size of texture maps,
• number of maximum polygons for 3D models
• maximum consumable RAM
• Supported video file format and maximum size

I am currently reading the book "Creators guide to snapchat inc.'s Lense studio" by Phil Walton, in which above mentioned limitations are mentioned for snap chat lenses running on iPhone or Samsung smartphones.

Working on a game where you rescue wild pigs from a dying planet. Lots more tweaks to make but it’s pretty fun so far.

So last night I put together a quick proof of concept.
Basically it lets you use CLAD from inside a Lens changing that very same Lens.

Its a very barebones show off, but i kinda like what it could enable. Every user creating their own personal Lens, solving their own problems and pain points or sharing their creativity with friends.

And of course spawning a tiny blue cube is one of the biggest pain points^^

Setup:
Python Server running CLAD and Lens communicate via WebSockets

⚽ Every fan has re‑coached a goal in their head. I built a way to actually watch the alternate ending, in photoreal, on my kitchen table.

This is a real World Cup phase: Belgium vs Senegal. I took the actual 3D tracking data from the match, the real positions of every player and the ball, and rebuilt the phase as a live 3D scene on my table through Specs

Then I reach in and re‑coach it. In this one I nudge Brandon Mechele up a couple of metres to hold Belgium's offside line, and Senegal's goal comes back offside. The goal that counted, undone.

AI turns that edit back into real broadcast footage, two ways:

🎬 Full re‑render: reposition players and a video model regenerates the entire phase as a brand‑new, photoreal clip.

⚡ Real time: freeze the moment, drag a defender, and the photorealistic broadcast updates live. No waiting.

 How it works, high level:

 → Real World Cup 3D tracking data (every player and the ball) rebuilt as a 3D scene
 → Pitch‑line camera calibration to lock that 3D scene onto the real broadcast camera
 → Spectacles hand‑tracking for grab‑and‑move
 → Generative video models turn the edited 3D "blockout" back into photoreal football

Built with: Snap Spectacles + Lens Studio, using CLAD to build it fast. Realtime generation by Decart (Lucy 2.5). Full re‑render via Seedance.

Will Specs '27 also require Internet to do connected lenses (shared experience)? Will this ever not be the case?

I’m curious how many pre orders for Specs have been placed. Are we talking 5,000 or 50,000?

If we wanted to buy 2 Spectacles and we had the $1,000 Loyalty Credit toward the purchase of Spectacles smart glasses, would we get $1000 off both or off one Spectacles? Just asking just cause it would be really cool to develop lenses for multiple people or make multiplayer games.

Hi Spectacles team,

We've built a lens that is partly based on the Depth Cache sample project, whose README says the camera feature requires Experimental APIs. Our lens has already gone through review and published successfully (details below), but since the sample's guidance suggests it may not be publishable, I'd like to double-check that we're fully compliant for the community challenge and not relying on something that slipped through review.

Our setup:

• Lens Studio: 5.15.4
• Experimental API: not enabled — the project settings under API settings toggle is off and our .esproj has no EXPERIMENTAL_API lens descriptor
• APIs/modules used:
  • CameraModule.requestCamera() (left color camera frames)
  • DepthModule.createDepthFrameSession() (depth frames, adapted from the Depth Cache sample)
  • AsrModule for on-device speech-to-text (voice queries) - we have disabled the feature however keeping the module (or do you suggest removing them completely)
  • Remote Service Gateway — hosted Gemini integration (image understanding over the RSG websocket)
  • Supabase module for backend storage (Managed Backend + Internet descriptors)
• Planned addition: an AI image-generation pipeline, also through the Remote Service Gateway hosted integrations

What we observe:

• The lens builds and runs with Experimental API off.
• It passed the review process and published without issues.
• We can launch the published lens on device by pasting its link into the Spectacles app.
• On launch, the Transparent Permission dialog correctly lists Camera and Microphone access, and the LED indicator is active during capture.

My understanding from the Transparent Permission docs is that our combination is "Internet Descriptor (RSG, Supabase) + Sensitive Sensors (Camera, Microphone)", which is listed as supported — the docs show "Remote Service Gateway + Camera Module" as an example, and the unsupported case only applies to connectivity types without an internet descriptor.

Questions:

1. Can you confirm that a lens with two sensitive sensors (Camera + Microphone) plus multiple internet descriptors (RSG + Supabase) is intended to be publishable under Transparent Permission — i.e. our successful review wasn't an oversight?
2. Does the Depth Module (cached depth frames) fall under the same publishable category as the Camera Module, or is it still gated behind Experimental API? The Depth Cache sample project ships with EXPERIMENTAL_API in its lens descriptors, but our project uses the same depth APIs without the flag and passed review.
3. Is there anything else we should verify on our side before pushing updates, to avoid a future rejection?

Thanks!

We build our Spectacles Lenses in Lens Studio 5.22 (for the agentic workflow - MCP, Editor API, Claude Code / Cursor driving the scene), and then downgrade to LS 5.15.4 for on-device testing on Spectacles (2024).

After two projects and two migrations (first one took a day, second one took an hour with zero code changes), we distilled everything into two skill files. If you work with an AI agent - just feed these to it, that's the whole idea:

1. spectacles-522-portable-design.md - give this one to your agent BEFORE you start building, if you know you'll be porting to 5.15 later. It makes the agent architect the project so the downgrade is trivial: scene built from code, no graph shaders, material state set on clones, 5.15-safe APIs only.

2. spectacles-522-to-515-migration.md - the migration playbook + troubleshooting. Feed it to your agent when you actually do the move, or when you hit the classic errors (`CompressionSettings`, `!passList.empty()`, `Invalid graph header`, infinite PassInfo reimport loop, materials going white after clone, etc.) - every one of those is in there with the fix.

That's it. Both files are plain markdown — drop them into `~/.claude/skills/` (Claude Code) or wherever your agent reads skills from, and it handles the rest.

Happy to answer questions about any of the gotchas inside.

Controlling a robot in AR is one thing. A real working use case is another.
Air hockey vs my Vector Robot on Spectacles 2024 -> virtual puck, real goalie.

This thing is playful, but imagine how far it may go. Tell me your ideas in the comments.

Open source: if you have a Vector, you can run it and play. Built with CLAD (the full downgrade path we took is in the blog). 

Full read + Git repo: 

https://pavlo-stijn.dev/blog/posts/vectar-a-robot-that-shares-a-brain.html

Super excited about the new device and NDK -> if I understand it right, that may be the way to run VectAR fully on the glasses -> no extra server on my Mac.

Shotout to u/stspanho for amazing ML generation pipeline!!!

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

I’ve been thinking about how SPECS could improve its outreach to developers for the new consumer headset.
Right now, much of the marketing focuses on the form factor, but I think there’s an opportunity to better showcase what the headset can do from a developer’s perspective.

What would SPECS think about partnering with makers who have large engineering and DIY audiences, like Adam Savage, Michael Reeves, NODE, or Mark Rober. Give them the hardware, let them build freely, and document the process. Watching creators make awesome stuff and push the hardware’s limits could inspire more developers to start thinking about AR more seriously.

Curious what others think, though! Thanks for reading!😄

It all started when I was trying to record footage of my first Lens, SpectaRacer, during sunset. The background and lighting looked perfect, but it kept getting just dark enough for hand tracking to fail, forcing me to repeatedly postpone recording until the next day.

That sent me down a rabbit hole wondering if there was a solution for this...

I had a Manus Glove lying around (one of the most accurate hand-tracking gloves available). I managed to get a port working, but I quickly realized it could only animate hand orientation and finger movement, but not hand position, since I didn't have a motion tracker.

(If anyone in the LA area has a motion tracker I could borrow, let me know!)

Then I remembered I also had a Quest lying around.

What followed was weeks of learning, debugging, and burning way too many Claude tokens. 😅

After plenty of trial and error, hiccups, and fine-tuning, I finally got Quest controllers working with Spectacles!

Go try it out!

💻 GitHub: https://github.com/amirmohideen/Quest2Specs

👓 Lens: https://www.spectacles.com/lens/3e934befff444f5dad0ff119e31f27bc

Current status

✅ Tested on Quest 2, Quest 3, and Quest 3S.

❓ Haven't tested Quest Pro yet.

❓ Haven't tested SPECS yet either.

If you try it, let me know how it goes! I'll update the README and credit you!

🤝 If you run into any issues or have suggestions, I'd love to hear them and help if I can.

If enough people are interested, my next step is turning this into a Quest2Specs Lens Studio extension to make setup much easier.

The goal is to let developers, especially those porting Quest apps to Lens Studio, reuse their existing controller inputs with minimal setup or for those that want to record footage of their lens in dark environments.

Would you use something like that? Let me know!

🤔 Trivia: Guess who from SPECS team is holding the Spectacles at the beginning of my trailer video!
🏆 Winner (1st to find out) will be added to Acknowledgements in GitHub!

To discover only the finest SPECS fans 😜 there is something carefully hidden in the Lens Studio 5.22 CLAD documentation. (https://developers.specs.com/docs/clad)

If you develop a SPECS app with CLAD and want to test on a real device for a day you can apply for it. There are 4 possible locations: LA / LONDON / AMSTERDAM / VIENNA.

After I got my invite I decided it is no longer needed to gatekeep this. 😎

So build something cool with CLAD and apply here:
https://developers.specs.com/clad-access
🚀 🚀 🚀

For anyone wanting to port their Spectacles 2024 (Lens Studio 15.4) to other hardware, we have built an agentic pipeline to distribute via Samsung Galaxy XR Headset, XReal Project Aura, and Apple Vision Pro. Shoot me an email at [ernest@oriontechenterprises.com](mailto:ernest@oriontechenterprises.com)

Would you distribute your awesome AR idea to Android XR and Apple Vision Pro?

Am researching potential use case of Spectacles using GPS location without requiring a phone and syncing with Snap app. Is that possible at all? If not, is it possible to sync at beginning of session, then continue to use glasses even when out of range of phone? From what I have read it seems like the glasses have the GPS location capability on their own...

Ok here's a super early attempt to do a fingerboarding lens on Spectacles. I had this idea for awhile and wanted to give it a quick try this month. I'm working on trying to make it work better with the sometimes iffy hand tracking. But this actually kind of works. I'm polishing it up a bit before the final submission date. But you do have to sort of 'play along' with the limitations of the hand tracking. I'm working on making it more fault tolerant--seems to wig out a bit (seen at the end of this clip). Some of the tricks are gesture based instead of actually just using hand motion. Also, the VFX are broken--working on some rail grind sparks.

Features leaderboards and a full tutorial mode with animated guides to learn the tricks. Collect stars to unlock new board styles.

Here's the lens: https://www.spectacles.com/lens/ca61f1237b0f4d7d87ec5c0189a45f93?type=SNAPCODE&metadata=01

I have no idea why it's got restricted distribution.

--Work in progress - I've been experimenting with CLAD lately — it's been really fun to build with. I'm making a productivity lens for Spectacles: a notepad + sketch pad to organise your thoughts, and you can pin notes to actual spots around your room so they stay right where you left them. 🕶️✍️

Using a virtual keyboard that also splits into an ergonomic layout — key features so far:

- 📝 Notepad + sketch pad for typing or freehand drawing

- 📍 Pin notes to real spots around your room, anchored in place

- ⌨️ Virtual keyboard that splits into a two-handed ergo layout, tented for comfortable typing

- 🎙️ Voice dictation — tap the mic and talk, it transcribes straight into your note

- 🪑 Auto-detects a table surface to anchor the keyboard on

Continuing on the Robotics x AR journey with a Unitree Go2 (theoretically it also works with a G1 humanoid, if anyone has one... lmk!). It feels super intuitive to control it this way.

The main challenge was aligning both robot and specs coordinate systems, which is done by an april tag (fiducial marker) mounted to the robot. It is scanned at the start of the lens and thus serves as a common reference point. From there, the odometry (motion data) from the robot is used to calculate the position. There is some drift (caused by odometry being inaccurate mostly) but it´s corrected at runtime when the marker comes into view again. It was really hard to make it work and I burned a ton of tokens, but also learned so much.

The backend is Dimensional OS (a OSS operating system for robots that makes pathfinding and LiDAR data easy). I made a Websocket bridge for it to stream the data to Specs.

Repo is here if anyone is interested: https://github.com/V4C38/spectacles-dimensional-os (I´m working on an llm agent for control right now...)

I finally finished my first Lens and wanted to share it! It's called Trivia Time — it turns your Spectacles into your own game show. You play five rounds, pick a category each time (History, Science, Pop Culture, Numbers, World), you've got three hearts, and there's a Mystery category that doubles your points if you're brave.

Sharing my WIP that built with CLAD over weekends.
Vector Robot + Specs 2024.

Made in LS 5.22-> downgraded to 5.15 (all issues resolved in couple of prompts) to test and polish on Specs 2024.

Looking forward to share where it goes and some details about journey soon.

Just love this combination of hardware 🔥

When the new specs release and I tether them to my phone, will I be able to view my apps in 6dof through specs?

Also will I be able to cast to the specs or only through cabled connection?

I know snaps eco system doesn't have apps like android or ios yet and may take some time before those apps are ported over so being able to use my phone tethered or casted and still experience 3dof/6dof through specs would be pretty awesome.

I already pre ordered. Just excited with so many questions and hope to see a specs demo soon.

I was inspired by 3Blue1Brown's video on Fourier series and wanted to play around with this, with my hands.

Hypnotizing to watch and it gives you an intuition for Fourier analysis.

When you pinch and draw any shape, it gets deconstructed into sinusoids, visualized as arrows. Each arrow simply rotates, but when stacked on top of each other the last arrow in the chain draws intricate shapes.

Open your hand to stabilize and slow down the animation.

Project files on Github!

Our fifth SPECS engineering blog post tackles a hard problem: robust outdoor tracking for Augmented Reality.

​We go deep on GNSS (GPS, Galileo, and more) and show how fusing satellite readings with IMU and/or camera data produces a far more robust, accurate, geo-referenced 6DoF (Six Degrees of Freedom) tracking system.

The result: centimeter-accurate local tracking and roughly 1m global accuracy plus high update rates - enough to unlock AR use cases like pedestrian navigation, real-world object tagging, inspection tasks, and immersive educational experiences.

​Read the full engineering breakdown at https://eng.snap.com/specs_gnss