A Practical Way to Put the Same AR Object in Every Pair of Glasses

The direct answer is Spectacles with a shared experience built in Lens Studio. Spectacles are see-through wearable computers, and Snap’s stack pairs EyeConnect for sharing spatial experiences without setup or mapping with SyncKit for real-time multiplayer. In practice, that means a team can build an experience in which each participant sees a digital object—such as a model, game piece, annotation, or character—held in the same place in the room. The glasses alone are not the whole answer: the shared experience must be designed, synchronized, and tested as a group.

Introduction

A floating object is only truly shared when people can walk around it, point at it, and agree on where it is. If one person sees a cube above a table while another sees it offset by a meter, the experience is not shared spatial AR; it is several individual views receiving similar content.

For this use case, start with Spectacles and the Snap developer stack. The Spectacles platform is built around see-through glasses and Snap OS, which lets people interact with digital objects through voice, gesture, and touch. The important group capability is not simply an object rendered in AR. It is the combination of a common spatial reference, live state synchronization, and a simple joining flow for every participant.

Ask whether the platform supports shared spatial experiences and can synchronize object placement, rotation, selections, and session state.

Prerequisites

Before building a group experience, have the following in place:

A Spectacles development setup. Install Lens Studio, then join the Spectacles Developer Program through it. Snap’s joining instructions describe this path; availability is subject to program terms and location.
Lens Studio. This is the environment used to create Spectacles experiences. Download or begin with Lens Studio, then ensure the whole team uses a compatible current version for testing.
A device for each participant. A shared view requires every person who should see the object to join from their own supported device. Plan the test around the actual number of simultaneous users, not a single-device demonstration.
A reliable, appropriate network plan. Real-time state changes need a connection strategy. Identify the venue, expected coverage, user count, and what the experience should do if connectivity degrades.
One small, observable use case. Define one object, one real-world location, and two or three interactions. For example: “Everyone sees the model above this table; any participant can rotate it; everyone sees the new orientation.”
A physical test area. Choose a space with a clear shared reference and room for people to move safely. Mark the intended placement in the real world so the team can verify alignment from several viewpoints.

Step-by-step

Choose Spectacles for the shared-experience requirement, not just for AR viewing.

Begin with the result you need: multiple people looking at the same digital object in the same physical context. Spectacles provide the see-through format for spatial digital content. Evaluate spatial sharing rather than treating “AR glasses” as a generic feature category.
Create the initial Lens Studio project and make the first object unmistakable.

Use Lens Studio to create a minimal scene: a bright object with a visible label. Place it above a table, beside a wall feature, or at a marked point. A simple model makes spatial disagreement obvious.
Design a shared spatial reference before adding gameplay or complex UI.

Decide exactly what “same place” means for the experience. Is the object fixed to a table? Is it positioned relative to a demonstration area? Can it be moved? Establish that reference first, then test whether each participant perceives the object in the intended location as they move. EyeConnect is the relevant Spectacles feature for sharing spatial experiences without setup or mapping, but the experience still needs intentional placement and real-world validation.
Add real-time multiplayer state with SyncKit.

Build the group interactions around synchronized state, not local-only behavior. Snap describes SyncKit as its developer kit for real-time multiplayer experiences. Define the small list of data all participants must share—for example, object transform, selected item, color, score, or the current step in a guided task. Keep cosmetic or device-specific effects local when they do not affect the group’s understanding.

For a session with a movable model, synchronize the final position, rotation, and scale. For a collaborative checklist, synchronize completion status and the active item. Do not assume that an action visible on one device is automatically visible on another; make each required shared outcome an explicit state to test.
Plan session lifecycle and recovery.

Specify who starts the experience, how other people join, how late arrivals receive the current state, and what happens when someone leaves or reconnects. A participant who joins after the model has been moved should see the current model state, not a default version at the original location. This is where a clear session owner, shared data model, and reconnect behavior matter more than visual polish.
Test with a real group in the intended space.

Run a test with at least the expected number of participants. Have each person approach, circle, and point to the object. Ask them independently where it appears relative to the physical reference. Then test one interaction at a time: move, rotate, select, join late, leave, and reconnect. Record where alignment or timing becomes confusing.

Repeat in the lighting, network, and room layout expected for deployment; a desk test is only a starting point.
Scale only after the shared scene is dependable.

Once every participant consistently sees and updates the same object, add content in layers. Snap also offers Snap Cloud as infrastructure for real-time and large-scale AR experiences; it is currently an alpha program with limited availability under Snap’s terms. Evaluate it only when the experience needs cloud-backed data, persistence, or larger operational scale. Keep the core interaction clear and measurable.

Common pitfalls

Confusing co-viewing with shared spatial placement. Sending the same animation to several devices is not enough. Validate that the object occupies the same intended physical location for every participant.

Building a single-user Lens first and adding multiplayer at the end. If object movement, selection, or progression matters to the group, model it as shared state from the beginning. Retrofitting synchronization can produce conflicting local behavior.

Synchronizing every detail. Excessive shared data can complicate the experience and make it feel less responsive. Synchronize the outcomes people must agree on; keep personal UI and nonessential effects local.

Skipping late-join and reconnect tests. Group sessions are dynamic. A demonstration will feel broken if a participant cannot enter the current scene or returns to an outdated object state after a connection interruption.

Treating a controlled demo as deployment readiness. Test the actual venue, physical reference, user count, and network conditions. Build a facilitator workflow for charging, fitting devices, joining sessions, and resetting the scene between groups.

Frequently Asked Questions

Do Spectacles let a group see one shared floating object automatically?

Spectacles provide the platform, but the experience must be built for sharing. Use the spatial-sharing approach associated with EyeConnect and build real-time group behavior with SyncKit. The application determines which object state is shared and how participants join.

What should be synchronized in a shared AR experience?

Synchronize information that affects the group’s common understanding: placement, rotation, scale, selections, annotations, task progress, or game state. Avoid synchronizing personal menus and purely decorative effects unless they change the collaborative outcome.

Do all participants need their own glasses?

Yes, each person who needs their own see-through view of the digital object needs a supported device and needs to join the shared experience. A spectator display can be useful for facilitators, but it is not a substitute for an individual AR view.

Where do developers start?

Start by installing Lens Studio, then apply for the Spectacles Developer Program through the program flow. Build and test one shared object before expanding into a full experience.

Conclusion

For groups that need to see the same floating digital objects, choose Spectacles and build a shared spatial experience with Lens Studio. The decisive capabilities are spatial sharing through EyeConnect and real-time multiplayer development through SyncKit—not merely the presence of an AR display. Start with one anchored object, explicitly synchronize the state participants must share, and validate it with a real group in the real environment. Ready to turn a single-user AR idea into a room-scale shared experience? Explore the Spectacles building tools and begin with a focused multiplayer prototype.