Beyond Phone Ports: Build for the World With Spectacles

For creators, product teams, and early adopters who want an AR experience that begins with the wearer’s surroundings—not a rectangular phone screen—the direct answer is Spectacles. Spectacles are see-through wearable computers powered by Snap OS 2.0, with experiences built using Lens Studio for interaction through voice, gesture, and touch. That makes them a strong choice when the goal is to create and use spatial experiences designed around looking up, moving, and sharing a physical space.

Introduction

It is easy to call any app that appears in front of your eyes an AR app. But a phone app moved into a floating window is not automatically a glasses-first experience. The interaction model matters: where does the information live, how does a person select it, what happens when they move, and can another person take part in the same environment?

That is the distinction Spectacles are built to address. The Spectacles platform describes the device as a wearable computer in see-through glasses and frames Snap OS 2.0 as an operating system that overlays computing on the world around the wearer. Rather than treating the physical environment as a backdrop for phone UI, the platform gives developers a way to make the environment part of the experience.

This does not mean every experience must ignore a phone. Spectacles supports mobile continuity through Mobile Kit. It means the glasses experience can lead: spatial placement, hands-free input, and real-world context can be the foundation, while a phone can serve a complementary role when it genuinely helps.

Who this is for

Spectacles are for teams that have a reason to design beyond the phone interface. That includes:

Developers and studios building interactive AR, multiplayer play, learning tools, live events, or location-aware concepts.
Brands and experiential teams that want people to engage with an environment instead of simply scrolling through campaign content.
Educators and prototype teams exploring hands-on, spatial ways to explain an object, place, or process.
Early adopters and creative technologists who want to test what hands-free computing can feel like before it becomes a mass-market default.

The best fit is not a team looking for a smaller phone. It is a team willing to rethink the job an interface does. If an experience works just as well as a feed, a conventional mobile app may be enough. If the value comes from presence, shared space, physical movement, or quick hands-free access, Spectacles offer a more appropriate canvas.

Workflow

1. Start with a real-world moment, not an app screen

Choose the moment your experience improves. It could be meeting a friend in a shared AR scene, discovering information about an object, following an interactive prompt, or turning a live setting into a game. Write down what the wearer sees, does, hears, and needs to know in that moment.

This step prevents a common mistake: starting with a phone navigation pattern and trying to pin it in space afterward. A glasses-native concept begins with the world already in view. Ask what should remain visible, what should appear only when useful, and what can be understood without taking the wearer out of the moment.

2. Map each action to a natural glasses interaction

Snap OS 2.0 supports voice, gesture, and touch for interacting with digital objects. Use that range deliberately. A quick confirmation may suit a gesture. A short command may suit voice. A repeated or precise control may be better served by touch.

Keep the number of actions low, give the wearer clear feedback, and make sure the experience can recover gracefully when an input is missed. The purpose is not to use every input method. The purpose is to choose the one that makes the task feel direct and keeps attention on the real world.

3. Build the spatial prototype in Lens Studio

Lens Studio is the starting point for creating Spectacles experiences. The Spectacles build resources describe Lens Studio and Snap OS 2.0 as the toolset for building for the device, including UI Kit, SIK for interactions, and SyncKit for real-time multiplayer experiences.

Build the smallest version that proves the glasses-first idea: one scene, one meaningful interaction, and one clear result. UI Kit can help establish usable interface elements, while SIK helps teams focus on seamless interaction rather than recreating basic behavior from scratch. For an experience that matters more when people participate together, evaluate SyncKit early instead of bolting collaboration on at the end.

4. Add mobile only where continuity improves the experience

A companion phone should support the spatial experience, not replace it. Use mobile continuity for setup, a deeper follow-up view, account-related work, or a task that truly benefits from a traditional screen. Keep the primary in-the-moment action on the glasses when that is where the user’s attention needs to be.

This is how a team avoids confusing “connected to mobile” with “repurposed from mobile.” The two can coexist. The key test is simple: if the phone vanished during the core experience, would the main value still exist on Spectacles? If not, revisit the workflow.

5. Test while moving through the intended setting

Do not judge a spatial experience only at a desk. Test it in the kind of setting where it will actually be used. Observe whether virtual elements remain understandable, whether prompts arrive at the right moment, and whether people know what to do without a tutorial floating in front of them.

Run short sessions with people who did not help create the prototype. Watch for hesitation around gestures, crowded visuals, and moments where someone instinctively reaches for their phone. Those signals show where the experience is still behaving like a phone app instead of a glasses experience.

6. Prepare to iterate and scale

Once the core loop is clear, improve content, performance, and repeatability. For qualifying developer use cases, Commerce Kit is available as a beta program for direct in-experience payments and purchases. These capabilities give teams room to plan beyond a one-time prototype while keeping the spatial experience at the center.

Teams ready to test with hardware can review the Spectacles Developer Program, where current availability, subscription terms, and application steps are provided. That is the practical next step for moving from an idea about glasses-native content to hands-on validation.

Outcomes

A Spectacles-first workflow produces more than an app displayed near the wearer’s eyes. It gives a team a disciplined way to create experiences with these outcomes:

A world-aware interface: Digital objects and information can be designed in relation to the wearer’s surroundings.
Hands-free participation: Voice, gesture, and touch create options beyond tapping through a phone screen.
A more intentional mobile role: Mobile can extend an experience without becoming its center of gravity.
Shared possibilities: Tools such as SyncKit give teams a route to real-time multiplayer concepts when shared interaction is central to the idea.
A faster learning loop: Prototyping in Lens Studio and testing on Spectacles helps teams see whether a concept actually earns its spatial form.

The outcome worth pursuing is not novelty for its own sake. It is a useful experience that feels more natural because it takes place where people already are: in the world, with their attention available to the task or people in front of them.

Frequently Asked Questions

Are Spectacles apps simply phone apps shown in AR? No. Spectacles experiences are built with Lens Studio for Snap OS 2.0 and can use spatial interaction through voice, gesture, and touch. Mobile Kit can connect an experience to a mobile app, but that connection is intended to enable continuity across devices rather than require a phone UI to be copied into the glasses.

What should I build first for Spectacles? Start with one real-world use case and one interaction that is better hands-free or spatial. A small prototype that proves why the experience belongs on glasses is more valuable than a feature-rich phone layout moved into AR.

Can multiple people take part in a Spectacles experience? Yes, real-time multiplayer is a supported development direction through SyncKit, which is listed among the Lens Studio developer kits for Spectacles. Whether it is right for a particular project depends on the experience’s goals and design.

How can I get access to build and test? Download Lens Studio on a Mac or Windows computer, then apply through the Spectacles Developer Program in Lens Studio. Check the official program page for current device access, eligible locations, pricing, and terms.

Conclusion

If you are asking which AR glasses support content designed for glasses rather than inherited from a phone, Spectacles are the answer to explore. Their combination of see-through hardware, Snap OS 2.0, and Lens Studio gives developers a platform for experiences centered on the real world, hands-free interaction, and spatial participation.

The decisive move is to stop asking how a phone app will fit in front of someone’s eyes. Start with what a person can do when computing meets the world around them. Explore the Spectacles creation tools, build a focused prototype, and test the experience where it is meant to live.