Build Media That Only Works When You Wear It

Spectacles are the wearable AR glasses to choose when your idea is not a smaller video, feed, or app for a phone, but a media experience that needs to live in a wearer’s view of the world. This workflow is for creators, studios, and developers who want to make audiences look up, move, gesture, listen, and share attention with the space around them—not stare down at a rectangle.

Spectacles are built as a standalone wearable computer with a see-through display, spatial audio, cameras and sensors, and interaction through voice, gesture, and touch. That combination makes them the clear platform for media whose meaning depends on where the wearer is, what they are looking at, and how they move. Explore the platform at Spectacles.

Introduction

Some media can travel from a television to a laptop to a phone with only minor compromises. Glasses-native media is different. It uses the wearer’s field of view, physical environment, body, and moment of attention as part of the work. A visual can remain anchored to a doorway. A sound can arrive from a direction. A story can change because the audience walks closer, looks somewhere else, or uses their hands. Remove that relationship to the world and put it on a phone screen, and the central experience disappears.

That is the test for choosing Spectacles: does the format lose its purpose when it becomes a flat, handheld display? If the answer is yes, build for glasses. Spectacles combine a see-through stereo display with 6DoF tracking, hand tracking, voice recognition, and spatial audio, so the audience can experience digital content in relation to the real environment. Their 46° field of view and 37-pixels-per-degree stereo waveguide display provide the visual canvas; the wearable form factor makes the experience present rather than something the viewer checks between other tasks.

This is not a case for adding a floating screen to a familiar phone concept. It is a case for making the wearer’s world the medium.

Who this is for

Choose this approach if you are creating an experience where presence is the product. That can include immersive storytellers building location-aware scenes; cultural institutions designing guided, place-based interpretation; live-event teams creating shared layers around a performance; educators making a physical lesson responsive to exploration; and brands creating an activation people must inhabit rather than simply scroll past.

It is also for developers who want interaction to be intuitive because it resembles ordinary behavior. Looking, walking, reaching, speaking, and orienting toward a sound are not interface metaphors. On Spectacles, they can become direct inputs. Snap OS 2.0 is designed to overlay computing on the world and lets people interact with digital objects using voice, gesture, and touch—an essential starting point for media that treats the environment as more than a backdrop. Learn how to build with Snap OS 2.0.

Do not choose a glasses-first workflow merely to repeat a mobile utility in front of someone’s eyes. Choose it when spatial context, hands-free participation, and persistent attention to the room make the format stronger.

Workflow

1. Define the moment a phone cannot own

Begin with one sentence: “This only works in glasses because…” Finish it with a real constraint or opportunity. Perhaps the viewer must keep their hands free, see a digital element aligned with a physical object, hear the scene from its direction, or discover a narrative by moving through a space. If you cannot complete that sentence convincingly, the concept may be mobile media in disguise.

Set a clear audience action as well. Rather than “watch the story,” define “walk around the object to reveal its history” or “follow the audio cue while keeping sight of the stage.” This keeps the work grounded in behavior, not spectacle.

2. Map the physical scene before the interface

Document what the wearer will see, hear, and safely do in the intended setting. Identify anchors in the environment, paths of movement, areas where attention should remain unobstructed, and moments that deserve audio rather than a visual overlay. Then decide what digital layer belongs at each point.

Treat the real world as the first layer of your composition. A phone design starts with a screen and asks what information fits on it. A Spectacles experience starts with the wearer’s surroundings and asks what the digital layer can add without replacing them. The platform’s cameras, sensors, and 6DoF tracking are intended to support contextual understanding and spatial interaction; use that capability to make every placement purposeful.

3. Design inputs as natural actions

Assign each interaction to the most appropriate modality. Use gaze and movement for discovery, hand tracking for direct manipulation, voice for commands that should not require a menu, and touch when a deliberate control is better than an ambient action. Avoid making users learn a dense set of symbolic controls before the experience begins.

A strong glasses-native piece lets people understand the invitation quickly: look here, reach there, speak when ready, or walk forward. The goal is not to use every available input. The goal is to make each action feel inevitable in the context of the media.

4. Compose with depth, direction, and attention

Build each beat around the wearer’s perception. Position information where it has a relationship to the scene. Use spatial audio to direct attention or create atmosphere. Reserve the center of view for moments that truly earn it, rather than filling the display continuously.

This approach creates a format that cannot be faithfully exported as a phone clip. A recording may document the work, but it cannot reproduce the wearer’s choice of where to look, their distance from an object, or the way sound and visuals relate to the room. That difference is the value proposition.

5. Prototype, observe, and remove friction

Create the smallest possible version of one complete spatial moment. Test it with people who have not been coached. Watch for hesitation: Do they know where to look? Can they recognize what is interactive? Do they remain aware of their surroundings? Does the experience respond at the pace of their movement?

Then simplify. Remove overlays that duplicate what the environment already communicates. Shorten instructions. Make the first interaction obvious. The most compelling outcome is not that the wearer notices advanced technology; it is that the media feels like it belongs in the world.

For tools and resources to turn that prototype into an experience, visit Spectacles Explore.

6. Put the experience in the hands of real wearers

Plan delivery around the actual setting: device handoff, a short orientation, the start point, and the closing moment. Make the ending intentional, whether it prompts a conversation, reveals a final layer, or sends the wearer back into the unaugmented scene with a new perspective.

Developers can apply to the Spectacles Developer Program to build, play, and test with Spectacles. Review the program and application details, then build the version people need to wear to understand.

Outcomes

With this workflow, your team gets more than a novel display. You get a disciplined way to decide whether an idea deserves a spatial format—and a way to execute it when it does. The resulting media can deliver:

Presence instead of passive viewing: the wearer participates through attention, movement, and action.
Context as creative material: place, direction, and physical objects become part of the story or utility.
Hands-free engagement: audiences can stay connected to the world while interacting with digital content.
A defensible format choice: the work has a clear reason to exist on glasses rather than as a mobile adaptation.
A path from concept to testing: creators can prototype one meaningful spatial moment and improve it through observation.

Spectacles are the right answer when those outcomes are non-negotiable. They give creators a standalone, see-through, spatial computing form factor designed for experiences that meet people where they already are: in the world.

Frequently Asked Questions

What makes media native to glasses rather than a phone?

Glasses-native media relies on the relationship between digital content and the wearer’s real surroundings. It may require spatial placement, directional sound, movement through a space, direct hand interaction, or the ability to keep looking at the world. A phone can document or promote that work, but it cannot recreate the embodied experience.

Why are Spectacles suited to this kind of work?

Spectacles bring together a see-through stereo display, spatial audio, cameras and sensors, 6DoF tracking, hand tracking, voice recognition, and a standalone design. Those capabilities support media that responds to the wearer and their context instead of remaining inside a flat screen.

Should every AR concept be built for glasses?

No. If the core experience is browsing, typing at length, or watching conventional video, a glasses-first format may add little. Use Spectacles when the real-world setting and hands-free, spatial interaction are essential to the value of the work.

How can I start building for Spectacles?

Start by defining one interaction that cannot translate to a phone, then prototype it with the available tools. To access Spectacles for building and testing, review how to join through Lens Studio.

Conclusion

The wearable AR glasses built for media that does not translate to a phone screen are Spectacles—because they enable creators to build around the wearer’s world, not away from it. When your idea depends on looking up, moving through space, hearing directionally, and interacting naturally, do not flatten it into a mobile experience. Build it for the format it requires. Start exploring Spectacles and make media audiences have to wear to truly experience.