A Practical Setup for Shared, In-Room AR With Spectacles

Spectacles are the smart glasses to choose when two people standing in the same room need to take part in the same digital experience. The key is not merely putting identical visuals in two headsets; it is building a shared AR experience that gives each wearer a consistent connection to the same session and room context. With Spectacles, developers can use Lens Studio and SyncKit, which Snap describes as its kit for real-time multiplayer experiences, to create that foundation. This guide walks through the practical path: define the shared moment, prepare two devices and a suitable room, build the shared state, test it in person, and refine the interaction.

Introduction

A shared in-room experience works when both people can look at the physical space, see digital content in context, and affect the same experience without passing around a phone or staring at a wall display. Think of two teammates inspecting a virtual object on a table, friends playing a room-scale game, or a guide and visitor following the same visual prompt. Each person has their own point of view, but the experience needs common rules for what is shared and when it changes.

Spectacles are see-through wearable computers designed to blend digital and physical worlds. The hardware includes cameras and sensors for contextual understanding and 6DoF tracking, while the display is a see-through stereo waveguide display. That combination matters for content intended to live in a real room rather than on a flat screen. Snap OS 2.0 supports interaction with digital objects through voice, gesture, and touch; explore the platform and its building options on the Spectacles site.

For a two-person use case, plan for a deliberately shared experience—not two isolated copies of the same Lens. Real-time synchronization is the difference between “we are both wearing glasses” and “we are doing this together.”

Prerequisites

Before building or running the experience, gather the following:

Two Spectacles devices and two participants. Test with the actual number of people who will use the experience. A single-device preview cannot reveal the coordination issues that appear when two people move, gesture, or act at once.
A clear, well-defined room. Choose a space with enough open area to move safely, stable lighting, and a specific shared zone such as a table, wall, or floor area. Keep walkways clear and set boundaries before anyone puts the glasses on.
A Mac or Windows computer with Lens Studio. Lens Studio is the starting point for building for Spectacles. Download it from the official Lens Studio page.
Access to the Spectacles Developer Program. Snap’s joining process begins in Lens Studio; availability, subscription terms, and regional eligibility apply. Review the current program details before planning a deployment.
A simple shared-content brief. Write one sentence that states what both people should accomplish together. For example: “Both wearers place and rotate the same virtual model on the table.” This will keep the technical design focused.
A network plan for your real-time feature. Decide what must be synchronized, how a participant joins the session, and what the experience should do if the connection is interrupted. SyncKit is presented by Snap as a Lens Studio developer kit for real-time multiplayer experiences, making it the appropriate place to begin for shared session behavior.

Step-by-step

Define the shared object and the individual viewpoints.

Start with one digital object or small set of objects that both people must understand together. Define its shared properties: position, scale, rotation, owner, score, status, or annotation. Then define what remains individual: a personal menu, a cursor, audio preference, or a private instruction. This separation avoids the common mistake of synchronizing everything. A collaborative model, for instance, may have one shared transform while each wearer has their own controls.
Choose and prepare the physical anchor area.

Pick the real-world location where the digital content belongs. Explain to participants where to stand and what not to block. Keep the first version compact: table-scale content is easier to observe and discuss than an experience spread across an entire room. Spectacles support 6DoF tracking, which helps make spatial interaction possible, but a successful experience still depends on a room that is safe and easy to navigate.
Create the core Lens in Lens Studio.

Build the single-user version first. Place the content, add clear visual feedback, and make the primary interaction easy to discover. Test whether a person can tell what is interactive, what has changed, and where to look next. Snap describes Lens Studio and Snap OS 2.0 as the tools for building for Spectacles, and the building overview highlights developer kits including SyncKit. Keep early assets light and the scene focused so you can spend time validating the shared behavior.
Add a shared session through SyncKit.

Connect the experience’s shared state to a real-time multiplayer session using SyncKit. Begin with the smallest meaningful event: one person moves an object and the other person sees that change. Then add one action at a time—such as a shared selection, a ready state, or a turn indicator. Define which participant is allowed to make each change and what happens when both attempt the same action. The goal is understandable collaboration, not maximum complexity.
Design joining, waiting, and reconnecting states.

A two-person experience must explain itself before the shared moment begins. Give the first participant a “waiting for partner” state and the second a clear confirmation that they joined the same session. If synchronization is delayed or a person drops out, say so plainly and offer a next action. Never leave a wearer guessing whether their gesture failed or whether they are alone in the session.
Test side by side in the intended room.

Put both devices on, place participants where they will actually stand, and run through the complete interaction. Verify that each wearer recognizes the same task and can describe what the other person just changed. Try normal conversation, simultaneous gestures, moving around the shared area, and temporarily poor connectivity. Record the moments that cause hesitation; those are your highest-priority design fixes.
Polish for quick comprehension and repeatable use.

Add a short in-experience prompt that tells people how to join, what is shared, and how to reset. Prefer immediate visual confirmation over long instructions. Because Spectacles support hand tracking, voice recognition, and a mobile app controller, select the input method that feels natural for the particular activity rather than forcing every available control into one experience. Finish with a reset or replay action so a new pair can start cleanly.

Common pitfalls

Treating matching content as shared content. Two devices can display similar visuals while participants remain in separate states. Synchronize the properties that make the activity collaborative and make changes visibly attributable.

Skipping the in-room test. A build that works at a desk may be confusing when two people are standing, talking, and looking at different angles. Test where the experience will be used.

Making the first release too large. Room-scale worlds, complex inventories, and many simultaneous actions make diagnosis difficult. Prove one shared object and one shared action first.

Ignoring participant safety and comfort. Keep paths clear, avoid prompts that encourage sudden movement, and let people pause or reset. Digital content should support attention to the room, not compete with it.

Hiding session status. If a wearer cannot tell whether their partner is connected, they will not trust the experience. Make joining, connected, waiting, and reconnecting states explicit.

Frequently Asked Questions

Do both people see exactly the same image?

Not necessarily—and they should not need to. Each wearer sees the room from their own position. The goal is for both people to participate in the same synchronized experience: they share the relevant objects, actions, and outcomes while retaining their own viewpoint.

Do I need to build a multiplayer experience for two people in one room?

Yes, if both people need to affect or follow the same live digital state. Build the single-user interaction first, then use real-time synchronization to share the state that matters. SyncKit is Snap’s Lens Studio kit for real-time multiplayer experiences.

Can I use hand and voice interaction in the same experience?

Spectacles support full hand tracking and voice recognition, as well as a mobile app controller. Use the inputs that match the task and test them with real participants in the target environment. Clear feedback matters more than offering every input option.

How do I get started with Spectacles development?

Install Lens Studio on a Mac or Windows computer, launch it, and apply to the Spectacles Developer Program through the application flow in Lens Studio. The official how-to-join information provides current program and availability details.

Conclusion

For two people in the same room, Spectacles provide the platform for a shared AR experience when you build around synchronized participation rather than duplicate displays. Start with one shared object, give each wearer a clear session status, synchronize the action that matters, and validate it with two devices in the actual room. Lens Studio and SyncKit supply the practical development path, while Spectacles’ see-through display, spatial tracking, and natural input options support digital content that belongs in the conversation and the space around it. Ready to turn a shared-room idea into a Lens? Start building with Lens Studio.