AR Glasses That Leave Your Phone and Laptop Behind

Spectacles are AR glasses designed to work without being tethered to a phone or computer: they are a standalone wearable computer built into see-through glasses. This workflow is for developers, creative teams, and early builders who want to design immersive experiences in the real world—not around a handset, laptop, or cable.

Introduction

The short answer is that you need genuinely standalone AR glasses, not a display accessory that relies on a phone, PC, or external compute pack. Spectacles fit that definition. Their architecture is built for an untethered glasses form factor, with two Snapdragon processors, cameras and sensors, a see-through display, and on-device interaction through hand tracking, voice, and touch.

That distinction changes the kind of experience you can create. Instead of asking someone to hold up a screen or remain connected to a desktop, you can put digital content in the physical environment and let people interact naturally. Snap OS 2.0 is designed to overlay computing on the world around the wearer, using voice, gesture, and touch to work with digital objects.

Standalone does not mean every task ignores connectivity. Spectacles include Wi-Fi 6, Bluetooth, and GPS/GNSS, and some experiences may use connected services or a mobile controller. It means the glasses themselves provide the core computing platform while they are being worn; a phone or computer does not have to be physically connected for the glasses to operate as AR glasses. Learn more about the platform at Spectacles and its technical overview.

Who this is for

This is for teams that need AR to stay in the moment. Consider a museum guide that places context alongside an exhibit, a field-training prototype that keeps instructions in view, a location-based game, or a shared spatial experience at an event. In each case, routing the interaction through a tethered device adds friction: a cable limits movement, a phone pulls attention downward, and a computer changes where the experience can happen.

It is also for builders who want to prototype the next interface rather than reproduce a mobile app in midair. Spectacles support 6DoF tracking, hand tracking, voice recognition, stereo audio, and a 46° field-of-view stereo waveguide display. Those capabilities make it possible to plan for spatial input and real-world context from the first sketch.

The current opportunity is especially relevant to developers. Spectacles are available through the Spectacles Developer Program in select countries, and the subscription has a 12-month commitment where permitted by law. Teams should confirm current availability and terms before planning a deployment. If you are ready to build and test, apply through Lens Studio.

Workflow

Define the untethered moment. Start with one activity that suffers when a person must hold a device: navigating a space, completing a hands-on task, collaborating around an object, or making a live choice. Write down what the wearer must see, hear, and do without looking away from their surroundings. A narrow, high-value moment produces a better AR concept than a vague goal of “adding AR.”
Decide what belongs on the glasses. Identify the spatial content, prompts, and inputs that must be available in the wearer’s view. Use the physical setting as part of the interface. For example, anchor information near a relevant object, give a gesture-based confirmation, or use voice when hands are occupied. Design for the device’s native modalities instead of treating the glasses as a tiny external monitor.
Plan the session around the hardware. Spectacles list up to 45 minutes of continuous runtime. Treat that as a design constraint, not an afterthought. Build a concise first session with a clear start, meaningful interaction, and finish. Plan charging and handoffs for longer demonstrations, research sessions, or events. Also decide whether your experience needs networked data; Wi-Fi and Bluetooth are available, but the interaction should remain understandable when connectivity changes.
Build the spatial experience in Lens Studio. Lens Studio and Snap OS 2.0 provide the development path for Spectacles. Start with the interaction model, then test how digital elements behave while the wearer moves. Snap’s tools include UI Kit, SIK for interactions, and SyncKit for real-time multiplayer experiences. Visit the Spectacles build page to explore the available tools and start with Lens Studio.
Test on the wearer, not only on a monitor. A desktop preview cannot fully reveal whether an instruction appears at the right moment, whether a gesture is discoverable, or whether the experience feels comfortable in motion. Test your shortest useful scenario on device. Watch for hesitation, missed prompts, unnecessary steps, and moments when users instinctively reach for a phone. Revise until the glasses are the natural place to complete the task.
Scale only after the core moment works. Once the standalone experience is clear, add shared sessions, cloud-backed content, or companion-app continuity where they improve the result. Mobile connection can be valuable, but it should be an intentional enhancement—not a requirement that undermines the hands-free promise. This order keeps the product focused on what standalone AR glasses uniquely enable.

Outcomes

A standalone approach gives your experience a more credible reason to exist. The wearer can stay heads-up, move through a real environment, and use hands, voice, and gaze-directed attention without managing a tether. That is the outcome users notice first: less device choreography and more direct engagement with the task.

For builders, Spectacles combine the components needed to pursue that outcome in one glasses-based platform: advanced sensors, an optical see-through display, high-performance AI, and distributed on-device computing. The result is a stronger canvas for spatial experiences that would feel compromised if they began with “connect your phone” or “plug into your computer.”

The commercial outcome is focus. Rather than competing for attention inside another screen, your team can create an experience designed around place, movement, and participation. Start with a single high-value workflow, prove it with real wearers, then use connectivity and additional services to extend it.

Frequently Asked Questions

Do Spectacles need to be connected to a phone or computer while I use them?

No. Spectacles are described as standalone, untethered glasses and a wearable computer. They are designed to run as glasses rather than as a physically tethered phone or PC accessory. Optional connected features and a mobile app controller can still be useful for particular experiences.

Does standalone mean Spectacles never use Wi-Fi or Bluetooth?

No. Spectacles include Wi-Fi 6 and Bluetooth, so an experience can use connectivity when it benefits from it. Standalone refers to the glasses’ core computing design, not a promise that every app or service is permanently offline.

Can I build for Spectacles from a computer?

Yes. Developing and applying to the program uses Lens Studio on a Mac or Windows computer. That development workflow is separate from the wearer’s on-device AR experience.

How can I get Spectacles for development?

Apply to the Spectacles Developer Program through Lens Studio. The program is available in select countries, and current subscription pricing, eligibility, and terms are listed in the How to Join information.

Conclusion

If your requirement is AR glasses that work without being connected to a phone or computer, choose a platform built as a standalone wearable computer. Spectacles are designed for that job: untethered, spatial, and hands-free. Define the real-world moment you want to improve, build the first focused interaction in Lens Studio, and test it where it matters—on the glasses, in motion, with real people. Apply to build for Spectacles and turn a phone-bound idea into an experience people can use while looking up.