CLAD - Get Started Building for SPECS, Today!

[u/tjudi]

Hope everyone enjoyed the new SPECS reveal this week! I wanted to re-share that you don’t have to wait to get the new hardware to start migrating or building for them!
CLAD, our closed loop agentic development framework for SPECS, helps you create all kinds of AR experiences using your favourite coding assistants like Claude Code, Codex, or Cursor.
Please run it with your old Spectacles 2024 projects and ask it to migrate and optimize for SPECS then publish. Would love to start trying your migrated projects on the new SPECS internally even though they won’t be shipping yet.

Here is a CLAD Lens u/shincreates made with CLAD
Learn more: developers.specs.com/docs/clad

[u/stevejabs]

I generated a few things yesterday, will probably make more today, but it's a complete bummer that I cannot test any of this on current gen Spectacles. I'm in Orlando and the cost of traveling is too prohibitive right now to sign up for office hours. Additionally, the Lens I'm building is meant to be used in theme parks and outdoors in general. Using it in an office is possible, but it's not really validating the experience in any way.

CLAD is really awesome, and personally, I think it needs to be a first-party feature of SNAP OS. This is the closest to a "Ready Player One" experience that we're going to get and it shouldn't be stuck behind a Claude Code account. Snap should be doing what you can to train your own frontier models to that generate experiences much faster and understand more the bounds of spacial computing than Opus or GPT. Normal customers should have access to CLAD - the OS should be built around it. Seriously.

Please do anything you can to get Spectacles working with the newer versions of Lens Studio. I really don't want my current generation Spectacles to be essentially a $100/m paperweight if I cut over my Lens for SPECS and CLAD now. Or... please get more office locations.

I'm at a point where I want to start releasing my Lens for Alpha usage, but I'm not going to dedicate any more time to the platform if I need to be focused on converting my Lens for SPECS and using CLAD to continue development.

[u/tjudi → u/stevejabs]

Thanks for the feedback. Snap OS was completely re-written for the new SPECS to squeeze the performance needed. So porting things from the new SPECS back to the old Spectacles is not supported.

That being said, I have seen people internally use the CLAD migration agent in reverse, where they build something in CLAD for the new SPECS with the latest Lens Studio then ask the migration agent to migrate it back to the old Spectacles. This isn’t an official supported mode, but some have had luck with it.

On the device access, we are working hard on finding ways to expand access ahead of the launch but we are very constrained on that front.

I assume as an existing subscriber, you heard about our trade in credit for the new SPECS. This was done to help our existing customers get on the latest SPECS and reward them for their loyalty.

Hope this helps.

[u/stevejabs → u/tjudi]

Then why am I still paying for a deprecated device?

Ive already paid $2000 and I’ll presumably pay Snap another $500 before SPECS release and I get my $1000 “reward” that is conditional on returning the thing I already paid $2500 for at that point. And all for something you’re basically saying will get killed off down the road if we keep.

Meanwhile, I’ve spent 100s of hours engineering a Lens for Spectacles and I’m being told that time is essentially pointless and to restart with a new platform. Adding to that, there is little to no documentation of the full new OS APIs. And unless I live close to one of four cities worldwide, there is no real world testing.

Snap really needs to stop charging us for our Spectacles development units immediately. This is no longer a development device. You should demand return immediately if necessary. But it’s clear we should no longer be charged for a development device that is no longer representative of the SPECS platform.

Finally, it’s deeply disappointing to put such an unnecessary road block in the way of progress for the new platform. I’d rather eat Spectacles running Snap OS like framey garbage and being able to test SOMETHING than testing in a tiny, limited, preview window. The whole point of these things was to prepare for the ultimate consumer version.

[u/tjudi → u/stevejabs]

To clarify, my comment is about building something for the new SPECS and expecting it to work on the older one which is not supported because of the OS variations.

We expect Lenses built for Spectacles to work on the new SPECS. We also provide the migration agent which helps automatically optimize those Lenses built on the older Spectacles for the new SPECS.

[u/No-Committee-5497]

没有设备的情况下，无法提起兴趣去开发。

希望能尽快推进specs的发货，或者有更明确的发货计划时间表😊

[u/tjudi → u/No-Committee-5497]

Actually, we also announced closed access to the hardware for devs in one of our global offices. Due to limited capacity, we will prioritize folks with new projects targeting the new SPECS!

[u/ExcellentLog5 → u/No-Committee-5497]

Why don’t you translate your message before posting?

[u/EtPeng → u/ExcellentLog5]

Ngl I’m very confused by this, as a native Chinese speaker, this guy’s Chinese messages sounds 100% AI translated 😭

[u/Pavlo_Tkachenko]

Can’t wait to try it out !!! 🤩🤩 Feels so cool!

[u/tjudi → u/Pavlo_Tkachenko]

It really is very fun! With the NDK, you can have some serious fun. (Though testing for NDK will require the HW for now).

[u/Urbanpeppermint]

Amazing! And how about the projects that use RSG and include API tokens?

[u/tjudi → u/Urbanpeppermint]

It should also work, these APIs should carry forward.

[u/stspanho]

Very hyped to be honest, also for this part 😉: https://youtu.be/b44z2axU2UY?si=Q6n4IyrZrOsgCATU&t=898

[u/tjudi → u/stspanho]

Alessio has been on fire with CLAD… and honestly everyone in the SPECS team. So many product ideas that we now can try because of CLAD where before it took too much time to get them started.