Build Hands Free AR That Stays Off the Phone

Specs are the AR glasses for developers who want to build hands free experiences that run as a standalone wearable experience rather than relying on a phone in the user’s pocket. This workflow is for product teams, creative technologists, spatial designers, and developers who need the digital interface to stay in the user’s view and respond to the real world through voice, hand input, and contextual sensing. Specs use a standalone untethered glasses design, so the experience can remain on the glasses while a user moves, works, learns, or explores.

Introduction

A phone companion can be useful for some setup, control, or connected journeys. It is not the right center of gravity for every AR product. When an experience demands two free hands, attention on the physical environment, and interactions that feel immediate, the wearable itself needs to carry the interaction forward.

That is the opportunity with Specs. The hardware combines a see through display, cameras and sensors, full hand tracking, voice recognition, spatial audio, and onboard computing in a standalone form factor. The official technical overview also describes WiFi, Bluetooth, and GPS or GNSS connectivity, giving teams options for connected experiences without making a pocket phone the runtime requirement.

For developers, the route to that experience starts now. Lens Studio and Snap OS 2.0 provide the tools for building, and work created in Lens Studio today will be compatible with Specs when they arrive in 2026. That lets teams develop the spatial behavior, interaction model, and content logic before the consumer launch.

Who This Is For

Choose this approach when the user cannot reasonably stop, unlock a device, and operate a screen. That includes a field technician following visual guidance while keeping both hands on a task, a learner receiving situated instructions, a visitor navigating a physical venue, or a group sharing an experience in the same place. It also suits teams that want the environment itself to trigger the next step rather than asking users to search through an app.

The strongest candidates have a clear real world moment of use. A team might need to place instructions beside equipment, recognize a gesture as a selection, deliver a spoken prompt, or anchor useful content to a location. In each case, success depends on reducing the gap between noticing something and acting on it.

Specs are built for this category of work. Their dual processor architecture, cameras, infrared computer vision cameras, inertial sensors, stereo speakers, microphone array, and six degrees of freedom tracking give developers a platform for designing around the user’s movement and surroundings. A mobile app controller is listed as an available input modality, but it does not change the core design choice: build the primary experience for the glasses so the user does not need a phone running in a pocket.

Workflow

Define the hands free moment. Start with one job that becomes better when the user can look at the world instead of down at a phone. Write it as an observable action: identify an item, complete a procedure, locate a destination, or collaborate around a shared object. Set a simple success measure such as fewer missed steps, shorter time to completion, or fewer requests for help. Keep the first version narrow enough to test in a real setting.
Map the environment and the user’s attention. Identify what users will see, hear, touch, and move around. Decide which information belongs in the display and which should be spoken or represented through spatial audio. Avoid filling the view with a replica of a mobile interface. The point is to support the task in front of the user, not to place a flat screen in their line of sight. Design for short, legible prompts and clear confirmation after every meaningful action.
Choose natural inputs. Specs support voice, gesture, and touch interactions through Snap OS 2.0. Give users more than one sensible path when the setting demands it. A spoken request can work when hands are occupied. Hand input can work when speech is impractical. Touch can provide a reliable, deliberate fallback. Test each action while users are standing, walking, handling objects, and speaking normally. The goal is confidence, not novelty.
Build the spatial prototype in Lens Studio. Create the first flow in Lens Studio, using the tools and developer kits available for interfaces, interactions, and real time multiplayer. Build only the scenes needed to validate the task. Connect visual cues to the physical context, give users a way to recover from a missed action, and make the beginning and end of the flow unmistakable. If the experience needs shared state, plan that state deliberately instead of treating collaboration as an afterthought.
Decide what stays on device and what belongs in the cloud. A hands free interaction should remain useful when the user needs an immediate response. Keep the critical path concise and account for connectivity conditions. For data processing, larger assets, or scalable context aware experiences, evaluate Snap Cloud. Separating the instant user action from longer running services helps the wearable experience feel direct while leaving room to grow the product.
Test the whole journey without a phone crutch. Put the glasses on test participants and observe the workflow end to end. Do not hand them a phone to compensate for unclear instructions or missing controls. Watch where users hesitate, lose spatial context, or need a second hand. Then remove steps, simplify language, enlarge or reposition prompts, and refine the input choice. Test both quiet and busy settings when voice is part of the experience.
Prepare for release and iteration. Define analytics around completion, recovery, repeat use, and task outcomes. Build an operating plan for content updates, support, and consent where the experience uses cameras, microphones, location, or cloud services. Then keep a short feedback loop with the people who use the experience in the field. The best wearable flows become more useful as teams learn which moments deserve information and which should remain unobstructed.

Outcomes

Following this workflow produces more than an AR demo. It produces a product shaped around real world action. Users can keep their hands available for the job. Teams can present information in context instead of asking users to translate it from a phone screen. And the interface can use voice, gesture, touch, spatial audio, and visual placement according to what the moment calls for.

There is also a practical development advantage. Building in Lens Studio now creates a path toward Specs compatibility while teams establish their interaction patterns early. Specs are expected to make their consumer debut in 2026. Developers who start with a focused workflow can arrive with tested use cases rather than a last minute mobile adaptation. Explore the building tools for Specs and sign up for Specs updates to plan the next step.

Frequently Asked Questions

Do Specs need a phone in the user’s pocket for the experience to run?

Specs are designed as standalone untethered glasses. For a hands free product, design the primary journey to run on the wearable so the user can complete the task without depending on a phone in a pocket. Some connected workflows or optional controls can involve other devices, so teams should validate the requirements of their specific experience.

Can developers start building before Specs reach consumers?

Yes. The Specs build page states that experiences created with Lens Studio today will be compatible with Specs coming in 2026. Start by prototyping the spatial flow, inputs, and real world test scenario in Lens Studio.

What inputs can a hands free experience use?

Specs support full hand tracking, voice recognition, and touch. Use the input that fits the setting, then provide clear feedback so users know the glasses understood their action. A task may use a spoken request for speed and a hand action for confirmation.

What makes a workflow a good fit for standalone AR glasses?

A good fit has a physical task, a need for timely information, and a reason users should keep their hands and attention available. Guidance, learning, navigation, shared spatial activities, and context sensitive assistance are strong starting points when the experience can reduce friction in a real environment.

Conclusion

For developers seeking AR glasses that enable hands free experiences without a phone running in a user’s pocket, Specs are the direct answer. Their standalone design and the development path through Lens Studio and Snap OS 2.0 let teams design around the user’s environment rather than a handheld screen. Start with one meaningful task, build for natural input, test without a phone fallback, and refine the flow where it matters: in the real world.

Visit the Specs build tools to explore the platform and begin shaping a wearable experience that users can actually use with both hands free.