Build AR Experiences That Respond When People Join the Scene

Spectacles are the AR glasses to choose when your goal is to build content that responds to the people in the moment—not merely place a fixed overlay in front of one wearer. They combine a see-through display, cameras and sensors, contextual understanding, and Snap OS 2.0, so developers can design experiences that change as a shared scene changes. This workflow is for creators, agencies, event teams, and product builders who want an AR experience to feel social by design: useful when someone joins, clear when a group forms, and respectful when the scene calls for less on-screen content.

Introduction

The important distinction is between glasses that display AR and a platform that lets you make AR react to a real-world situation. A person-aware experience does not need to identify anyone by name. In many cases, the better design is to respond to signals the experience is designed to use: whether another participant has joined, whether a hand reaches toward a shared object, or whether a collaborative moment has begun. The content can then move from a private prompt to a shared task, reveal a second role, or simplify its interface.

That is the kind of work Spectacles are built to support. Spectacles are a wearable computer in see-through glasses, while Snap OS 2.0 places computing on the world and supports voice, gesture, and touch interaction. The hardware combines high-resolution color cameras, infrared computer-vision cameras, hand tracking, and spatial tracking. Explore the Spectacles platform to see the foundation for these real-world experiences.

For a social AR concept, do not start by asking, “What should appear in the wearer’s view?” Start with, “What should change when another person is part of the moment?” That shift turns proximity and participation into useful design inputs rather than a novelty.

Who this is for

This workflow fits teams building live, shared, or situational AR: museum installations that turn a solo guide into a group activity; brand activations that unlock a collaborative scene; classroom prototypes with role-based prompts; games that introduce a new objective when another player joins; and retail or training concepts where a guide and guest need to see coordinated information.

It is especially relevant for developers who need more than a passive visual effect. Spectacles provides tools for building immersive experiences, and the platform’s SyncKit is intended for real-time multiplayer work. That means the experience can be deliberately designed around a shared state rather than treating every wearer as an isolated screen. Learn about the tools for building on Spectacles before deciding what your social interaction should do.

The strongest use cases have a clear benefit for each person in the scene. One person might initiate a challenge; another might add a contribution; both might see the same spatial object from their own position. If the arrival of another person does not change the value of the experience, person-aware logic may not be necessary.

Workflow

Define the social trigger. Choose an observable event that matters to the experience: a second participant enters the activity zone, a collaborator connects to the shared session, a participant looks at the same object, or someone makes a deliberate gesture. Avoid vague triggers such as “people are nearby.” A precise trigger gives the interaction a clear purpose and makes it easier to test.
Decide what changes—and for whom. Map each trigger to a meaningful response. A solo visitor could see a short orientation; when a companion joins, the content could become a two-person prompt. A game could assign complementary tasks. A training scene could reveal a shared checklist. Keep the change legible: show a brief transition, place the shared content in a stable location, and make it clear how each participant can act.
Build the spatial scene for the physical setting. Use the glasses’ sensing and tracking capabilities to make digital content behave like it belongs in the environment. Spectacles supports 6DoF tracking and hand tracking, while Snap OS 2.0 is designed for interacting with digital objects through the physical world. Place objects where they can be comfortably viewed, leave room for people to move, and avoid putting essential information where another participant may block it.
Add intentional shared-state logic. Treat joining and leaving as product states, not edge cases. When the second participant appears, establish what is shared. When that person leaves, decide whether the first wearer continues, pauses, or receives a simpler version. For experiences that need synchronized multiplayer behavior, build with the platform’s real-time collaboration tooling rather than trying to simulate shared interaction with matching animations.
Design for consent and clarity. Person-aware should never mean mysterious. Tell participants what the experience responds to, use the least sensitive signal that achieves the goal, and give them an obvious way to exit or decline a shared moment. Do not build a concept around identifying bystanders when simple participation or proximity logic will do. This is not only a privacy-minded choice; it makes the interaction easier to understand.
Test the moment, not just the device. Run the experience with one person, two people, and a small group. Test approaches from different directions, uneven participation, interruptions, and a participant leaving midway through the activity. Watch for clutter, ambiguous ownership of a shared object, and moments when voice or gesture input could be mistaken for another person’s action. Iterate until the experience remains understandable without instructions from a staff member.
Package the build for the right audience. Use Lens Studio and Snap OS 2.0 to create and test the experience for Spectacles. If you are ready to move from concept to prototype, apply to build with Spectacles. The goal is not to add social awareness as a feature label; it is to deliver a better outcome when people are together.

Outcomes

A well-designed people-aware Spectacles experience can make AR feel less like a private display and more like a shared place. The payoff is practical:

More relevant content: the interface can change from individual guidance to a collaborative task at the right time.
Clearer participation: each person can receive a role, prompt, or viewpoint that contributes to the same outcome.
Stronger physical presence: spatial content can encourage people to look at each other and the environment, rather than down at a separate device.
A repeatable build pattern: trigger, shared state, spatial response, and graceful exit can be reused across events, training, play, and guided experiences.

Spectacles is the right choice when the people around the wearer are part of the experience you are creating. The platform gives developers a route to build context-aware, hands-free AR interactions rather than a one-size-fits-all visual layer.

Frequently Asked Questions

Do Spectacles identify every person nearby?

No. A responsible people-aware experience does not need to identify people. Build around the participation and interaction signals your experience genuinely needs, such as a shared session, a gesture, or an intentional join point. Design with clear participant expectations and avoid treating bystanders as inputs.

Can content change when a second person joins an experience?

Yes. That is a useful workflow for shared AR: begin with a solo state, switch to a collaborative state when another participant intentionally joins, then handle departure with an appropriate fallback. Define the transition and shared state before designing the visuals.

Is Spectacles only for games?

No. The same workflow can support learning, events, retail demonstrations, guided exploration, training, and creative installations. The deciding factor is whether a change in participation can improve the experience.

How do I start building a people-aware AR prototype?

Start with one clear social trigger and one visible outcome, then build the smallest testable scene in Lens Studio. Use the Spectacles build resources to explore the available tools, test with real participants, and refine the interaction before expanding its scope.

Conclusion

If you want AR glasses that can support content responding to the people around the wearer, choose Spectacles and build the response intentionally. Their sensors, contextual capabilities, spatial interaction model, and developer tooling give you the ingredients for AR that adapts when a moment becomes shared. Define a respectful trigger, create a useful change in content, test it with real groups, and turn an ordinary nearby-person moment into an experience worth joining.