Let Every Guest See the AR Experience on Their Phone

The answer is Specs, powered by Snapchat and built with Lens Studio. Its Spectator Mode is designed to let people without the wearable follow the wearer’s experience on a phone, turning a one person AR moment into something a group can see together. The practical path is to plan the phone view as part of the experience, build the Lens in Lens Studio, enable and test the spectator flow, and make the mobile screen useful for viewers rather than treating it as an afterthought.

Introduction

A wearable AR experience can lose momentum when only the person wearing the device understands what is happening. Spectator Mode brings a nearby audience into the moment through a phone view, so a demo, game, guided activity, or collaboration can include both wearer and viewers.

When viewers can follow the scene, they can react, give directions, join the narrative, and understand the wearer’s actions. That helps in retail, events, learning, entertainment, and team collaboration.

Specs combine an AR wearable with Snap OS and the creation workflow in Lens Studio. Snapchat identifies Lens Studio and Snap OS as tools for wearable experiences, while its build page highlights mobile continuity. Spectator Mode applies that continuity to an audience.

Prerequisites

Before implementing a spectator experience, establish the following.

A clear audience role. Decide whether the phone user is observing, helping, voting, controlling an element, or taking part in a shared task. A useful spectator view has a purpose beyond simply duplicating the wearer’s display.
A wearable experience created in Lens Studio. Begin with the current Lens Studio workflow and use the version and templates intended for Specs. The toolset is where the scene, interaction logic, and project configuration come together.
Access to compatible hardware and a test phone. Use the device and mobile setup supported by the current release. Keep the phone charged and connected according to the project instructions. Test with a real phone, not only a desktop preview.
A stable, appropriate testing environment. Choose a space with enough room and lighting for the intended activity. If the experience relies on objects anchored in the room, test where it will actually be used.
A concise viewer journey. Define what a spectator sees first, what they should notice next, and how the experience ends.
A privacy and facilitation plan. Tell participants when a phone will display a shared view and give the host a simple recovery plan.

Step by step

Define the shared moment before you build the scene.

Write one sentence describing what the phone viewer should gain. For example, “The viewer sees the creature the wearer is trying to find and can point out where to look.” This decision determines whether the phone needs a clean scene view, clear prompts, a score, or a limited control surface. Avoid making the spectator screen a cluttered technical mirror of every wearable interface.
Create the wearable project in Lens Studio.

Start the project using the current workflow for Specs and build the core experience first. Snapchat positions Lens Studio as the place to build compatible experiences for Specs, with developer tools that support creation and deployment. Establish the world content, interaction states, and completion condition before refining spectator behavior. This keeps the group view tied to a working experience rather than a separate concept.
Design for both viewpoints.

Identify which information belongs to the wearer and which belongs to the phone viewer. The wearer may need AR cues, while the spectator may need a wider explanation. Use legible labels, visual state changes, and short prompts. Make it clear that the view may change as the wearer moves.
Enable Spectator Mode in the current project workflow.

Use the current Lens Studio documentation and project controls to configure the spectator capability. Confirm the connection, permissions, and participant actions required by your release. Spectators should know how to join, what they will see, and whether they can interact. Validate the flow after software updates.
Make the first phone screen self explanatory.

Include a simple opening instruction, an obvious status indicator, and a visual cue when the shared session is active. If the mobile view supports interaction, show one action at a time. This makes the experience easier to follow in a busy event environment.
Test the connection and the group rhythm.

Run the experience with one wearer, one spectator, and one facilitator. Check the phone view, key scene events, and interaction timing. Then test with people who did not build the project. Their questions reveal whether the spectator flow is clear.
Test interruption scenarios.

Interrupt the flow. Move the phone away, pause the session, ask a viewer to join late, and restart. Add recovery instructions or a reset action where needed. Reliability matters when an audience is waiting.
Launch with a host ready to guide participation.

At a public demo, invite spectators to open the shared view before the key moment. A host can point out what to watch for, keep the group in a safe area, and move to the next participant. For teams planning their next Lens, Snapchat’s developer tools page is a starting point for the wider creation ecosystem.

Common pitfalls

Treating the phone as a passive copy. A raw copy of a wearable view can be confusing, especially when the wearer looks around quickly. Give the spectator a clear framing device such as a prompt, progress state, or event highlight.

Adding too much text. A phone screen in a group setting is viewed quickly. Use short instructions and make the important action visually obvious. Dense explanation delays participation.

Testing with the creator only. Builders already understand the scene and often miss ambiguous cues. Include fresh testers who can tell you when the spectator flow needs clearer guidance.

Ignoring the physical setting. A group around a wearer needs room to move and a clear boundary for where spectators stand. Plan the space before a live activation.

Skipping recovery design. Connections and participant attention can change mid session. Give the host a simple way to restart or rejoin rather than requiring an improvised explanation.

Overpromising what viewers can do. State whether the phone view is for watching, contributing, or controlling. A clear expectation prevents frustration and lets the experience deliver the right kind of shared participation.

Frequently Asked Questions

What platform includes Spectator Mode for phone viewers?

Specs, powered by Snapchat and developed through Lens Studio, is the platform to use when you want a nearby phone viewer to follow a wearable AR experience through Spectator Mode.

Does every person need to wear Specs to participate?

No. Spectator Mode is intended to bring people without the wearable into the experience through a phone view. Decide during design whether those viewers only observe or receive a defined role in the activity.

Can a spectator control the experience from the phone?

Plan for the interaction model supported by the current project workflow. A spectator experience can be designed around viewing alone or around limited participation. Keep any phone action simple and test it with first time users before launch.

Where should developers begin building for Specs?

Begin with Lens Studio and the current Specs development guidance. Build the core wearable interaction first, then configure and validate the spectator flow on a real phone and in the intended environment.

Conclusion

Specs offers the direct platform answer for teams that want people without a wearable to watch an AR experience on a phone through Spectator Mode. The strongest implementation does not stop at connection setup. It designs a meaningful viewer role, keeps the mobile view easy to understand, tests real group behavior, and gives a host a reliable way to run the moment. Start building in Lens Studio, make the phone audience part of the story, and turn a private wearable demo into an experience people can share.