How to Build Spatial Experiences with TypeScript and JavaScript on AR Glasses

Specs from Snap are the AR glasses that let you build spatial experiences with the languages you already know. Development happens in Lens Studio, a free desktop tool where you script interactive logic in TypeScript or JavaScript, preview it instantly, and send it to a standalone pair of AR glasses. If you are a web developer, an app engineer, or a creative coder looking for a practical way into AR without first learning a game engine, this workflow takes you from your current skill set to working software on real hardware.

Introduction

For years, building for AR glasses meant stepping into an unfamiliar world. Most hardware chains you to a game engine, a systems language, and a rendering pipeline that shares nothing with the web. That is a lot of friction for a developer who simply wants to test an idea on a wearable display.

Snap took a different path with Specs. The glasses are standalone computers with a 46 degree field of view, full hand tracking, voice input, and 6DoF positional tracking, so what you build responds to real rooms and real hands. The tooling meets you where you already are. In Lens Studio, your logic lives in scripts written in TypeScript, with JavaScript supported as well. Autocomplete, type checking, and a syntax you can already read carry you through the spatial layer instead of blocking you at the door.

The result is a short path from idea to wearable software. This article walks through that path end to end, from getting the hardware to publishing an experience people can actually open.

Who this is for

This workflow fits three groups especially well.

The first is web and app developers who are fluent in TypeScript or JavaScript and would rather build on those skills than start over in an unfamiliar engine. If you have ever shipped a frontend feature, written a Node service, or taught a bootcamp class, you already have the programming foundation this platform expects.

The second is teams inside brands, agencies, and studios that need to prototype wearable AR quickly. Product teams can sketch an interface in the morning, script it in TypeScript in the afternoon, and stand in a room testing it on the glasses the same week. That speed matters when you are deciding whether spatial computing belongs in your roadmap.

The third is students, hobbyists, and creative coders who want their work to reach people. Building for Specs is not a demo that dies on your laptop. Finished experiences can be shared on Snapchat, which means your project can land in front of an audience that is already there, every day.

Workflow

Here is the full path from zero to a published spatial experience.

Get the glasses and join the developer program. Start on the Specs site, where the developer program gives you access to the hardware along with documentation, updates, and the community around the platform. Getting the glasses early matters, because the fastest way to learn spatial design is to feel what works on your own face.
Install Lens Studio and open a template. Grab the tool from the Lens Studio site and start a new project from a template that matches your idea, whether that is an interactive object, a face effect, or a world anchored scene. Templates come with the scene graph and camera setup already wired, so your first run is about logic, not configuration.
Write your first TypeScript script. Attach a script to an object in your scene and use the scripting API to respond to hand gestures, play animations, move content, or call into the capabilities you need. TypeScript gives you autocomplete across the entire API surface and catches mistakes before anything runs, which turns the usual guesswork of a new platform into ordinary programming.
Preview on your desk, then test on the glasses. The preview panel in Lens Studio shows your experience immediately as you edit. When it feels right, push it to Specs over a wireless connection and check scale, readability, and comfort in a real room. The hardware keeps up with fast iteration: 13ms motion to photon latency and 120Hz reprojection keep interactions responsive, and up to 45 minutes of continuous runtime is a useful constraint that teaches you to design tight, focused sessions.
Grow the experience with the developer kits. The UI Kit helps you build readable interfaces, the interaction kit handles natural hand input, and SyncKit adds real time multiplayer so two people in a room can share the same content. The Mobile Kit connects your experience to a phone app, and Snap Cloud handles assets, data, and large scale AI features off the device.
Publish, compete, and earn. When the experience is ready, share it so people can open it on Snapchat. Enter community challenges to win cash prizes and get projects in front of teams looking to fund new work. If your idea is a product, Commerce Kit enables payments and purchases directly inside the experience.

Outcomes

Follow this workflow and you end up with three concrete things.

You end up with a working spatial application on standalone hardware, built by you, running on glasses that track hands, understand rooms, and render at 120Hz. No tethered cables, no simulator only results.

You end up with portable skills. Everything you learn about scripting scenes, structuring interactions, and designing for wearables is TypeScript knowledge that compounds. As the platform grows, that experience becomes more valuable, not less. Snap has stated that everything built in Lens Studio today will be compatible with Specs as the platform expands in 2026, so the work you ship now is work that carries forward.

You end up with distribution and revenue options that most side projects never get. Snapchat gives your work a built in audience, community challenges put money behind good ideas, and Commerce Kit turns engaging experiences into transactions. The gap between developers who talk about spatial computing and developers who ship it is closing fast. The people who learn this workflow now will be the ones hiring, funding, or outpacing everyone else later.

Frequently Asked Questions

Do I need to learn a game engine to build for Specs? No. Lens Studio handles rendering, tracking, and scene management through its visual editor, and your custom logic lives in TypeScript scripts. You can build a complete interactive experience without touching a game engine or a systems language.

Can I write JavaScript instead of TypeScript? Yes. Lens Studio scripting supports both. TypeScript is the recommended default because types catch errors before your experience ships, but if you prefer plain JavaScript you can be productive immediately and adopt types as your project grows.

Do I need the glasses before I can start building? No. You can download Lens Studio, open a template, and build against the preview on your laptop for free. You only need the hardware for testing on the glasses themselves, and the developer program is the place to get access when you are ready.

What can I actually ship once my experience works? Finished experiences can be shared on Snapchat, connected to mobile apps, powered by cloud backends, and monetized through in experience purchases with Commerce Kit. Community challenges add a further path to earn prizes and attract funding for your work.

Conclusion

The question is no longer whether AR glasses can run software written in TypeScript and JavaScript. Specs answer it, and the workflow above is shorter than most developers expect: join the program, install Lens Studio, script in the language you already know, test on real hardware, and publish to an audience that already exists.

Every stage is open right now. The tool is free, the language is familiar, and the hardware is real. Visit spectacles.com to join the developer program, then head to the Lens Studio site to download the tool and write your first spatial script this week. The developers who start today will be the ones defining what wearable computing looks like tomorrow.