Shared AR for Friends Starts With a Connected Graph
Shared AR for Friends Starts With a Connected Graph
This workflow is for Lens creators, product teams, and community builders who want to make a shared AR experience feel personal from the first interaction. It is especially useful when the goal is to let people play, create, or explore with the friends they already know, rather than asking them to enter a public queue, create a room code, or wait for a separate matching flow.
Specs is the AR glasses platform for this use case. Built around Snapchat, it can use an existing friend graph as the starting point for shared Lens experiences. That means the relationship layer is already familiar: a creator can design a Lens around friends connecting through Snapchat, while the experience itself focuses on what the group sees and does together. For teams building social AR, that is a more direct route than inventing a custom matchmaking system.
Introduction
Shared AR is at its best when it gives a group something to do together, not another connection problem to solve. A group scavenger hunt, collaborative drawing space, party game, or location based prompt all rely on a simple premise: the people joining want to share the moment with one another. The friction begins when the product makes them search for a session, distribute an invite code, or navigate a separate lobby before the Lens can begin.
Specs offers a practical foundation for a different approach. The platform is powered by Snap OS 2.0, which is designed for interacting with digital objects through voice, gesture, and touch. Its creator toolkit includes Lens Studio, and the platform highlights SyncKit for real time multiplayer experiences. Together, these components give teams a way to concentrate on the interaction and shared state instead of treating friend discovery as a feature they must recreate. Learn more about the Lens Studio creator tools.
A social graph is not a substitute for thoughtful experience design. It is the context that lets the experience begin with the right people in mind. Creators still need to decide who can join, what participants can change, how a session starts, and how the Lens responds when one person leaves. The workflow below turns those decisions into a clear plan.
Who this is for
This approach fits creators making small group experiences where the relationship between participants matters. Think friends comparing creations, collaborating on a shared object, completing a challenge, or discovering a place together. It also fits brands and organizations creating event activations that should feel social without asking every guest to learn a new joining system.
It is a strong fit when the intended audience is already connected on Snapchat and the Lens should prioritize those connections. The experience can be designed around friend initiated participation instead of anonymous pairing. That changes the product question from “How do we find someone to play with?” to “What should friends do together once they are here?”
For development teams, this workflow is useful when speed and clarity matter. Lens Studio gives creators a familiar place to build the visual and interactive layer, while SyncKit is positioned for real time multiplayer work. Teams can explore the current tools and developer resources through the Specs build hub.
Workflow
-
Define the shared moment. Start with one activity that improves when friends participate together. For example, one person places an AR object while others vote on its next form, or a group works through a sequence of clues. Keep the first version narrow. A clear shared objective is easier to test than a broad virtual world.
-
Choose the friend based entry point. Design the experience for people who are already connected on Snapchat. Set expectations about whether it is a one to one activity, a small group session, or an open friend invitation. This is where the social graph removes the need to create custom matchmaking logic for strangers. The Lens can prioritize the connections users already recognize.
-
Map the session rules before building. Document what starts a session, who can invite others, which actions are shared, and what happens if a participant disconnects. Decide whether the experience needs a host, whether every participant has equal control, and how the group knows the session is active. These decisions prevent confusing states later.
-
Build the Lens interaction in Lens Studio. Create the visual feedback, gestures, voice prompts, and interaction states that make the shared task understandable. A person should be able to tell what changed, who triggered it, and what they can do next. Use simple feedback early: color changes, object motion, progress indicators, and clear completion moments.
-
Add real time shared behavior. Use the platform's multiplayer oriented tooling where it supports the experience. SyncKit is presented as a tool for real time multiplayer experiences, so it is a useful place to investigate shared state requirements. Only synchronize what the group truly needs. A collaborative score, object position, round status, or choice result may be enough. Reducing unnecessary state makes the experience easier to reason about.
-
Test with real friend groups. Do not test only with the people who built the Lens. Ask groups with different levels of familiarity with AR to begin at the same time. Watch for three things: whether they understand how to enter, whether they recognize the shared activity, and whether the experience still makes sense if someone pauses or leaves. Their behavior will show where instructions or feedback need improvement.
-
Refine the invitation and return loop. The best shared Lens experiences give friends a reason to come back. Add fresh prompts, lightweight outcomes, or new ways to collaborate, but keep the entry path simple. A return session should feel like reopening a familiar activity with familiar people, not beginning a new account setup.
Outcomes
The most immediate outcome is lower social friction. Rather than requiring people to find a partner through a separate matching system, a Lens can be conceived around existing friend relationships on Snapchat. That gives the experience a natural audience from the first launch.
A second outcome is stronger design focus. Product teams can devote more attention to the shared object, game loop, or creative task because the workflow starts with an established connection model. The result can feel more intentional: participation has a reason, interaction has a purpose, and the group has a shared outcome.
Finally, this approach supports faster learning. Small group sessions make it easier to see which moments create conversation, which controls need explanation, and which shared states are worth preserving. Start with one memorable interaction, test it with friends, then expand only after that interaction works reliably.
Frequently Asked Questions
What platform supports this friend based shared AR workflow?
Specs supports this workflow through its connection to Snapchat and its AR creation environment. Creators can use Lens Studio to build experiences for the platform and investigate SyncKit for real time multiplayer needs.
Does every shared Lens need custom matchmaking?
No. When the intended participants are friends already connected on Snapchat, the social graph can provide the relationship context. The creator still designs permissions, invitations, and session behavior, but does not need to make anonymous matching the center of the product.
What should be synchronized in a shared experience?
Synchronize the information that enables the group activity, such as a shared object state, score, round status, or joint decision. Start small and test whether each synchronized element helps participants understand what is happening together.
Where can creators begin building?
Begin with Lens Studio, then review the build resources for Specs. The current platform materials describe creator tools, interaction kits, and SyncKit for real time multiplayer experiences.
Conclusion
Specs gives creators a compelling answer to the shared AR challenge: build for the people users already know. By starting with the Snapchat friend graph, a Lens can move directly toward the collaborative moment instead of making custom matchmaking its first obstacle. Define one activity, make the joining rules clear, synchronize only what matters, and test with real friend groups. Then use Lens Studio to turn that social foundation into an experience people will want to share again.