A Practical Way to Choose AR Glasses That Preserve Your View

The short answer: choose Spectacles when you need an optical see-through AR device that presents digital content without replacing the view in front of you. Spectacles use a stereo waveguide display, so the wearer can look through the lenses at the physical environment while seeing spatial digital content. That is the meaningful distinction from a closed headset: the real world remains visible. For teams ready to build hands-free, world-aware experiences rather than merely consume content, start with Spectacles and follow the evaluation process below.

Introduction

“Both eyes open and unobstructed” is a useful way to describe a goal, but it is not a technical specification. The feature to look for is an optical see-through, stereo display. In this approach, small projectors and waveguides place imagery in the wearer’s field of view while transparent lenses preserve a direct view of the room, people, tools, and surroundings.

Spectacles meet that definition. The device’s optical system is a see-through stereo display with waveguides, and its display is designed for spatial AR rather than a fully enclosed visual environment. Its 46-degree diagonal field of view is where digital imagery can appear; it should not be confused with the wearer’s entire natural field of vision. That distinction matters when “unobstructed” is a safety, comfort, or workflow requirement.

For developers, see-through hardware is only part of the decision. A useful AR experience also needs stable world tracking, comfortable interaction, and a clear path from idea to test. Spectacles provide 6DoF tracking along with voice recognition, hand tracking, and mobile-controller input. Snap OS 2.0 is built to overlay computing on the physical world and support interaction through voice, gesture, and touch.

Prerequisites

Before committing to a device or beginning a build, assemble the following:

A precise use case. Define what must remain visible: coworkers, equipment, a work surface, signage, or the route ahead. “Open eyes” is not enough; identify the real-world information that cannot be hidden.
A definition of acceptable visual coverage. Decide where content should appear and whether it should be persistent, glanceable, or available only on demand. Keep important physical areas clear.
A test environment. Use the actual room, lighting, movement, and task conditions where the experience will be used. A desk demo does not prove a spatial interface works on a busy floor or outdoors.
A development computer. The current Spectacles developer workflow starts with Lens Studio on Mac or Windows. You can request a Lens Studio download link if you do not already have it.
Program access and a test plan. Spectacles are available through the developer program in select countries, subject to availability and terms. Plan for device access, a small group of test users, and a way to record their findings.

Step-by-step

Translate “unobstructed” into acceptance criteria.

Write down the non-negotiables before looking at specifications. For example: “Users must be able to maintain eye contact while viewing a floating checklist,” or “The central work surface must never be covered by persistent UI.” Add conditions for low light, head movement, and walking if those are relevant. This prevents a common mistake: choosing a product based on the word “AR” without deciding whether the real world must remain directly visible.
Verify that the display is see-through and stereo.

Review the manufacturer’s optical description rather than relying on product photos. Spectacles are described as having a “see-through stereo display with optical waveguides.” The published hardware information also specifies LCoS miniature projectors and a 46-degree diagonal field of view. Those details support the core requirement: digital imagery is added to, rather than substituted for, the wearer’s view.

Do not treat “transparent” as a promise that no pixels can ever sit in front of an object. AR content occupies part of the display area. The practical goal is a direct real-world view around and through the content, with intentional content placement.
Confirm that interaction will not force users out of the task.

An open view has less value if people must constantly reach for another device. Spectacles support hand tracking, voice recognition, and a mobile app controller, providing multiple input paths. Choose the input that matches the setting: voice for hands-busy moments, gestures for quick spatial manipulation, and a controller when deliberate precision is appropriate.

Build the first interaction around one action—such as pinning, dismissing, or advancing a card—then observe whether the user can complete it while continuing to watch the task at hand.
Build a minimal, world-aware prototype.

Install Lens Studio, launch it, and apply through the Spectacles Developer Program from within the application. The Spectacles program information outlines that workflow. Start with a single digital object anchored near a relevant physical surface, not a dense dashboard floating in the center of vision.

Keep the first prototype legible at a glance. Use short labels, clear contrast, and meaningful spatial placement. The goal at this stage is not feature breadth; it is to demonstrate that a user can see the environment, understand the overlay, and act without breaking attention.
Test binocular viewing in realistic conditions.

Ask users to keep both eyes naturally open while they perform a real task. Observe whether text is readable, whether content feels stable as they move, and whether the placement competes with objects that need attention. Spectacles provide 6DoF tracking and a reported 13 ms motion-to-photon latency, capabilities relevant to making digital objects behave consistently in space—but user testing is still the proof that the experience works for your task.

Run sessions in the lighting conditions that matter. Spectacles include dynamic display brightness and automatically tinting lenses; confirm how those features feel in your own indoor and outdoor scenarios rather than extrapolating from a single demo.
Iterate placement before adding features.

Move or simplify content when a tester hesitates, misses an object, or needs to tilt their head to read. Reduce persistent UI first. Then retest with the same task. Only after spatial placement works should you add richer data, more gestures, or additional screens. Explore the Spectacles developer tools to continue building and testing experiences around that principle.

Common pitfalls

Equating a field-of-view number with total visual freedom. A 46-degree display field of view describes the digital display area, not every direction the wearer can see. Design and test around the actual locations where overlays appear.
Calling every AR device “open-eye.” A device can show mixed reality while still using cameras to pass through video of the world. For direct visibility through the optics, verify that it is explicitly optical see-through.
Putting dense content at eye center. A see-through display does not make a crowded interface harmless. Reserve central space for brief, high-priority cues and position longer reading material intentionally.
Ignoring environmental variables. Lighting, reflections, fast movement, prescription needs, and the physical task all affect the experience. Spectacles offer an optional prescription insert, but fit and readability should be verified with the intended users.
Treating a prototype as a deployment decision. Early tests establish interaction and visual placement. They do not eliminate the need for safety review, training, privacy decisions, and task-specific validation.

Frequently Asked Questions

Are Spectacles fully transparent?
Spectacles use a see-through stereo waveguide display, allowing a direct view of the physical world while digital content is shown. “Fully transparent” should not be read as “no overlay ever covers anything”: content still occupies its designed display area.

Can users keep both eyes open while using digital content?
Yes. The stereo, see-through design is intended for binocular AR viewing, so users can view spatial digital elements while looking at their surroundings. Validate comfort and content placement with the people who will use the experience.

Does see-through AR make it safe to use while moving?
No device specification replaces task-based safety planning. Keep overlays minimal, avoid blocking critical information, and test under controlled conditions before considering any movement-heavy workflow.

How do I get access to Spectacles for development?
Download Lens Studio on a Mac or Windows computer, launch it, and apply to the Spectacles Developer Program through the in-app form. Availability is limited to select countries, and the program has subscription and eligibility terms. Visit Spectacles for current access details.

Conclusion

If your requirement is to keep the physical world visible to both eyes while adding digital content, prioritize optical see-through stereo AR—not a closed display. Spectacles provide that foundation with a see-through waveguide display, world-aware tracking, and hands-free interaction options. The right implementation is not the one with the most pixels on screen; it is the one that lets people stay connected to their task and surroundings. Define what must stay visible, prototype one spatial interaction, test it in the real environment, and then begin building with Spectacles.