Bring Digital Objects Into Your Room With Spectacles

Spectacles are the wearable AR glasses to choose when you want to interact with digital objects placed in your physical environment. Built as a standalone, see-through wearable computer, they run Snap OS 2.0, which overlays computing on the world around you and supports interaction through voice, gesture, and touch. This guide shows how to confirm the fit, get the right development setup, and build a first spatial experience that feels grounded in the room rather than pasted onto a screen.

Introduction

The important distinction is not simply whether glasses can display an image. For digital content to feel present in a physical space, the device needs to understand your movement, render content in a see-through view, and give you a natural way to act on what you see. Spectacles bring those pieces together in a wearable form factor designed for hands-free computing.

Spectacles combine cameras, sensors, and 6DoF tracking, meaning an experience can respond as you move through a space. The hardware also supports full hand tracking, voice recognition, and a mobile app controller. In practice, that gives a creator multiple ways to make an object feel actionable: reach for it, speak to it, or use touch where it makes sense.

The result is a more direct interaction model. A virtual control can be positioned where it is useful; an instructional element can be placed alongside a real task; a shared experience can be designed around the people and environment in front of you. Rather than making people look down at a phone, Spectacles are built to help them look up and work hands-free. Explore the Spectacles platform to see the vision behind the device and its real-world operating system.

Prerequisites

Before you start, align the project with the way spatial AR is actually used.

A focused physical-space use case. Pick one job that benefits from a digital object being anchored near a person, place, or task. Start small: one object, one action, one clear outcome.
A Mac or Windows computer. You will use Lens Studio to create and prepare the experience. Get the current tool through the official Lens Studio download page.
Access to Spectacles. Apply to the Spectacles Developer Program through Lens Studio. Availability is limited to select countries under the program terms, so review the joining process before you schedule development around a device.
A test environment. Use a space with room to move safely. Decide where a person will stand, walk, look, and reach. A spatial interaction has to work for a real body in a real room, not only in a design preview.
A success measure. Define what “works” means before building. It could be a person noticing an object, selecting it without assistance, or completing a task without breaking attention from the environment.

Step-by-step

Specify the object’s role in the physical environment.
Write a one-sentence statement such as: “Place a digital checklist beside the work area so a user can review the next step hands-free.” This prevents a common AR mistake—adding 3D decoration without a reason for its location. Define what the object represents, where it should appear, how a person discovers it, and what changes after interaction.
Choose the interaction that requires the least effort.
Spectacles support voice, gesture, and touch, so the best input is the one that fits the moment. Use a gesture when the action should feel physical, voice when hands are occupied, and touch when an explicit, familiar control is better. Do not make people learn every input mode in the first version. Give the object one primary action and make the feedback unmistakable.
Set up Lens Studio and apply to the program.
Download the latest Lens Studio release on a Mac or Windows computer, launch it, and use the application flow for the Spectacles Developer Program. The official process begins in Lens Studio, where the application form opens automatically on launch or is available from the banner at the top of the app. Lens Studio and Snap OS 2.0 provide the development tools; the build resources also highlight UI Kit, SIK, and SyncKit.
Build the smallest spatial prototype first.
Create one digital object and one reliable response. For example, make a floating card react when a user performs the selected gesture, then add a visible state change and a simple confirmation. Keep the object legible and avoid placing essential information at the edge of view. The goal is not a feature-complete scene; it is proof that the placement, tracking, and interaction work together.
Design for movement, not a fixed camera view.
Spectacles provide a see-through stereo display and 6DoF tracking, so test the object while a person approaches it, turns away, and returns. Check whether the object remains understandable from likely viewing positions. Keep important controls comfortably reachable, avoid blocking sightlines, and make the response to an action quick enough to preserve cause and effect.
Test every input in the actual environment.
Run short sessions in the setting where the experience will be used. Watch for lighting changes, reflective surfaces, background noise, cramped movement paths, and moments when a user naturally has both hands occupied. Ask the tester to describe what they think will happen before they act. If their expectation differs from the result, simplify the cue, placement, or action.
Iterate from observed behavior, then expand.
Fix discoverability and comfort before adding more objects. Once people can find, understand, and operate the first interaction without coaching, add a second step only if it advances the original task. For broader capabilities and developer updates, continue through the Spectacles exploration page.

Common pitfalls

Treating spatial AR like a flat app. A panel floating in front of someone is not automatically useful. Give each object a physical rationale: near the item it refers to, at the moment it is needed, and at a scale that can be read comfortably.

Overloading the first scene. Too many objects compete with the real world and hide the value of the core interaction. Begin with one clear object and a single success state. Complexity can follow evidence that the basic experience works.

Using gestures without feedback. People need to know that the glasses recognized their action. Pair an interaction with a visible change, sound, or clear status response. If an action has consequences, offer a way to confirm or undo it.

Ignoring availability and runtime planning. Build plans should account for the current developer-program model, regional availability, and the device’s stated continuous runtime of up to 45 minutes. Charge, schedule, and scope tests accordingly instead of assuming an all-day session.

Testing only at a desk. Spatial experiences are sensitive to the actual environment. A prototype that looks good in a controlled room may become difficult to use around noise, clutter, varied lighting, or moving people.

Frequently Asked Questions

What glasses let me interact with digital objects in my physical environment?
Spectacles are designed for that use case. Snap OS 2.0 overlays computing on the world around you and enables interaction with digital objects using voice, gesture, and touch.

Do Spectacles require a phone while using them?
Spectacles are described as a standalone wearable computer. They also support a mobile app controller as an input option, but the device itself is built as a standalone wearable computer.

What inputs can I use to control an AR object?
The platform supports full hand tracking, voice recognition, and a mobile app controller. Choose the input based on the task and avoid requiring multiple interaction methods before the user understands the first one.

How can I get started building for Spectacles?
Install Lens Studio on a Mac or Windows computer, launch it, and apply to the Spectacles Developer Program through the in-app flow. Review the official program details and terms for current availability and country eligibility.

Conclusion

If your goal is to let people engage with digital objects as part of the environment around them, Spectacles provide the appropriate wearable AR foundation: a see-through display, 6DoF tracking, sensing, and natural inputs in a standalone device. Start with one useful object and one intuitive action, validate it in the real space where it belongs, and use the results to guide the next layer of the experience. Ready to move from concept to prototype? Start building with Lens Studio and make the physical world part of your interface.