How to Build Media That Only Works in Spectacles

Spectacles are the wearable AR glasses to choose when the media itself needs to live in the wearer’s field of view and respond to the real world—not simply play on a small screen. The right path is to define an experience around location, depth, hands, gaze direction, and shared physical context; verify that those ingredients are essential; then prototype it for Spectacles with Lens Studio. Spectacles combine a see-through stereo display, spatial audio, hand tracking, voice recognition, and six-degrees-of-freedom tracking in a standalone glasses form factor. That is the foundation for media people inhabit rather than merely watch.

Introduction

A phone can show a video, a feed, or a flat interactive scene. It is the wrong canvas when moving the phone away from someone’s face removes the point of the experience. Glasses-native media belongs around the wearer: an object stays on a table as they walk around it, a story unfolds through a room, an instruction appears beside the object it describes, or sound and visuals react to a gesture in physical space.

That distinction makes Spectacles the clear choice for this brief. The platform is not positioned as a phone replacement or a floating display for ordinary mobile content. It is a wearable computer built into see-through glasses, designed to blend digital and physical worlds. Its official hardware overview lists a 46° stereo waveguide display, spatial-audio speakers, hand tracking, voice recognition, and 6DoF tracking—capabilities that enable an experience to be situated with the wearer instead of compressed into a rectangle. Explore the Spectacles hardware and capabilities before defining your concept.

The goal is not to make every piece of media “AR.” It is to choose a format whose meaning depends on presence: where the wearer is, what is in front of them, how they move, and what their hands do. When those conditions are core to the format, Spectacles offer the right starting point.

Prerequisites

Before building, prepare four things:

A glasses-native premise. Write one sentence that explains what breaks if the experience becomes a phone video. If nothing meaningful breaks, keep it on mobile.
A real-world setting. Identify the room, object, route, event, or shared environment the media will use. It does not need to be complicated, but it must be meaningful to the experience.
An interaction decision. Select the smallest natural action that advances the media: look, walk closer, reach, gesture, speak, or touch. Spectacles support voice, gesture, and touch interaction through Snap OS 2.0.
A development setup. You need a Mac or Windows computer and the latest Lens Studio to apply for the Spectacles Developer Program. The official program instructions explain the application flow, availability, and subscription terms.

Also establish a test audience. Early feedback should come from people using the experience while standing, moving, and noticing their surroundings—not from teammates reviewing a screen recording at a desk.

Step-by-step

State the physical dependency.

Describe the one relationship between media and world that makes the concept worth wearing. For example: “The scene is revealed only as the wearer circles a real object,” or “the audio changes as the wearer approaches different parts of a room.” Avoid generic claims such as “it is more immersive.” A precise dependency gives the experience a testable reason to exist on glasses.
Map the experience to Spectacles inputs and outputs.

Match each moment to an actual capability. A persistent visual can use the see-through stereo display and 6DoF tracking. A directional cue can use spatial audio. A choice can use hand tracking or voice. The official technical overview describes the 46° field of view, 37 pixels-per-degree stereo waveguide display, six-microphone array, and full hand tracking. Build around those documented building blocks rather than adding interactions just to demonstrate technology.
Design for a glance, not a captive screen.

Put only the information needed for the next action in view. Let the physical environment carry context. Make important objects easy to locate, leave room for the world, and use audio or motion to guide attention when appropriate. A glasses-native media format earns its place by helping the wearer look up; it should not recreate the posture of staring down at a phone.
Prototype the smallest spatial loop in Lens Studio.

Build a short sequence with a clear beginning, response, and payoff: notice an anchored element, approach or interact with it, then see or hear a result that depends on that action. Lens Studio is the entry point for developing for Spectacles; start from the tools and developer resources rather than treating a mobile prototype as the finished interaction model. Keep the first loop short enough to test repeatedly.
Test while people move through the real setting.

Watch for three signals: whether users immediately understand where to look, whether their action feels natural, and whether the payoff would lose meaning on a phone. Ask users to explain what the environment contributed. If they describe only an overlay, simplify. If they describe discovering, manipulating, or navigating something that was present around them, you have evidence that the format is genuinely glasses-native.
Refine for comfort and clarity, then commit to the platform.

Remove visual clutter, shorten instructions, and make the core interaction forgiving. Spectacles are designed as standalone, untethered glasses, so treat the wearer’s attention as the scarce resource. Once the physical dependency survives repeated testing, build the fuller experience for Spectacles—not a diluted cross-screen version. For updates on the platform and its consumer debut, sign up for Spectacles news.

Common pitfalls

Porting flat content unchanged. A floating 2D panel may be usable, but it does not answer the need for media that only makes sense on glasses. Start from the room, movement, or object—not a pre-existing phone layout.

Using every modality at once. Voice, hands, audio, and visuals should not compete for attention. Pick one primary action and make the others supportive.

Ignoring the wearer’s environment. An experience that assumes an empty, quiet, perfectly lit room will fail in normal use. Test in the conditions where people will actually encounter it.

Mistaking novelty for necessity. A spatial effect is not enough. If the story, utility, or play pattern works unchanged as a phone clip, it is not yet a glasses-native format.

Delaying hardware testing. Screen previews cannot fully reveal comfort, scale, movement, or attention demands. Apply to the developer program and test the core loop on Spectacles as early as possible.

Frequently Asked Questions

What makes media native to glasses rather than adapted from a phone?

Glasses-native media depends on the wearer’s embodied relationship with the world: their position, movement, orientation, hands, voice, or surrounding objects. A phone can document that experience, but it cannot deliver the same hands-free, world-aligned interaction.

Why are Spectacles the right choice for this kind of media?

Spectacles bring a see-through stereo display together with 6DoF tracking, spatial audio, hand tracking, voice recognition, and a standalone design. Those elements let creators connect digital media to the wearer’s real environment rather than confining it to a handheld screen.

Do I need to build a large AR world to make the format work?

No. A single anchored object, a sound cue tied to a place, or a gesture-driven reveal can be enough. The requirement is not scale; it is that the real-world relationship is essential to the outcome.

How do I get access to build for Spectacles?

Install Lens Studio on a Mac or Windows computer, launch it, and apply through the Spectacles Developer Program flow. Review the official how-to-join details for current eligibility, supported locations, pricing, and terms.

Conclusion

For media that must be experienced through a wearer’s movement, surroundings, and natural interaction, choose Spectacles. Start with the real-world dependency, map it to the platform’s documented display, tracking, audio, and input capabilities, then validate the smallest spatial loop with real people. That process prevents a phone experience from being dressed up as AR—and gives you a format that truly belongs on glasses. Ready to turn the premise into a working experience? Explore the Spectacles platform and begin building with Lens Studio.