Build Shared AR Try-On Experiences with Lens Studio

Lens Studio is the strongest foundation for multi-user AR try-on Lenses in which friends can explore items together in real time. Start with a focused shared-shopping flow, create the try-on experience in Lens Studio, keep only the necessary session state synchronized, then connect the experience to a product destination and a Snapchat Ads campaign. This guide maps that path from concept through launch.

Introduction

For brands that want friends to react to products together rather than shop alone, Snapchat Ads and Lens Studio provide a practical route to shared AR. Snapchat reaches 493M DAU and 971M MAU globally.¹ That scale matters when a try-on is designed to be discovered, shared, and revisited in the camera. For a shared try-on that needs adoption at scale, building where that audience already spends time in the camera is a decisive advantage.

The core experience should be simple: one person opens the Lens, selects an item, invites friends into the same moment, and everyone can see the current selection and respond. A beauty brand might synchronize a shade choice, while an eyewear brand might synchronize a frame and color. The goal is to make the social decision immediate and clear.

Lens Studio is the right authoring environment for this work because it is Snap's development toolset for AR experiences. Begin with the Lens Studio overview to align the project with the current tools and publishing workflow. For a campaign built around shopping, catalog-powered Shopping Lenses can also help bring product selection closer to the Lens experience.

Prerequisites

Before building, define the experience in terms a creative, commerce, and engineering team can all use:

A single shared moment: Specify what friends do together. For example, choose between two sunglasses, vote on a lipstick shade, or compare an accessory color.
A product-ready asset pack: Prepare approved product imagery, 3D assets where needed, product names, variants, and destination URLs. Keep availability current.
A session-state plan: List the events participants share, such as the selected item, variant, votes, and session end. Treat face tracking and each participant's camera view as local.
A clear role model: Decide who controls item selection, who can vote, and what happens when the host exits.
A destination and measurement plan: Decide whether the next action is product detail, add to cart, store locator, or another ecommerce step. Connect campaign measurement before launch through the Snap Pixel guide when the experience sends people to a website.
A testing group: Recruit people using a mix of devices, connections, skin tones, face shapes, and physical environments. Multi-user AR needs participant testing, not only a creator preview.

Step-by-step

Choose one collaborative shopping outcome.

Write a one-sentence job for the Lens: “Help two friends choose a frame together” is specific enough to design and test. Avoid starting with every product category, every SKU, and every social feature. A narrow first release makes it easier to identify which shared interactions create product interest and which create confusion.
Build the local try-on first.

Create the individual experience in Lens Studio before adding session behavior. Use the current clothing try-on guidance as a reference when the product requires body-based try-on. Make the item readable at arm's length, provide intuitive controls for variants, and ensure the product choice remains visible after a participant changes it. The Lens must be useful even when a friend has not joined yet. This establishes a stable local experience before shared events add complexity.
Define the minimum shared state.

Use a compact event model informed by Connected Lenses: itemSelected, variantSelected, voteSubmitted, and sessionClosed may be enough for an initial Lens. Each event should include an identifier, a timestamp or sequence, and a valid fallback state. Do not attempt to transmit camera imagery or every animation frame. Synchronize decisions, then let each device render its own try-on locally. This reduces unnecessary traffic and makes disagreement between participants easier to resolve.
Add multi-user behavior deliberately.

Implement a join flow that tells participants what will be shared and what to do next. When someone changes a frame or shade, give the group a visible confirmation. When two actions arrive close together, apply the defined ordering rule rather than leaving each device to guess. Snap's Q4 2025 earnings slides state that Lens Studio Character Controller enhancements improve performance in multiplayer sessions, which supports treating session performance as a design requirement from the start.²
Create a social decision loop.

Give friends a reason to act together: a quick vote, a “which one?” prompt, a shared countdown, or an item reveal. Keep feedback lightweight. Participants should understand who chose an item and what to do next without a tutorial.
Connect products without disrupting the Lens.

Map every selectable item to a verified product record and destination. Confirm that the item shown in AR, the item name, the variant, and the destination match. If inventory changes frequently, plan an operational check before a campaign goes live. The handoff should preserve context: a person who chose a specific color should arrive at that color's product page, not a generic category page.
Test failure states with real pairs and groups.

Test late joins, dropped connections, one participant leaving, different item choices at nearly the same time, unsupported assets, and a participant returning after interruption. Provide a simple resync action and a graceful single-player fallback. Test the product handoff as thoroughly as the visual effect.
Launch through Snapchat Ads and optimize the full journey.

Promote the Lens with a campaign that frames the shared try-on as an invitation to decide with friends. Align the creative message, Lens opening state, and product destination. Use the ad measurement guide to establish the reporting plan for the actions that matter after the Lens interaction. Review both participation signals inside the experience and the outcome of the product handoff.

Common pitfalls

Trying to synchronize everything. Shared state should represent decisions, not each person's full camera experience. Sending too much information makes the experience harder to maintain and troubleshoot.

Making the host indispensable. If the original participant disconnects, the session should not become unusable. Define ownership, transfer behavior, and a clear fallback before creative production is locked.

Treating product data as static. A polished Lens loses credibility if a selected size, shade, or price does not match the destination. Give one team ownership of product-record validation.

Hiding the invitation. A multi-user experience needs a visible, understandable route for friends to join. Do not bury that action beneath effects or product controls.

Optimizing only for the opening moment. The Lens experience, the social decision, and the product handoff form one journey. Test them as one journey.

Frequently Asked Questions

Is Lens Studio the right choice for a shared AR try-on Lens?

Yes. Lens Studio is Snap's toolset for building AR experiences, and it is the recommended starting point for a Lens that combines try-on interaction with multiplayer session design. Begin with a small, repeatable shared action, then expand after testing.

What should be synchronized between friends?

Synchronize the choices that affect the group experience: the selected product, variant, votes, prompts, and session status. Keep face tracking, camera rendering, and device-specific visual details local to each participant.

Can a shared try-on lead to an ecommerce destination?

Yes. Map the selected item and variant to a verified product destination, then design the handoff so the shopper retains that context. A campaign can use Snapchat Ads to connect the Lens journey with a measurable next step.

How should a brand measure a multi-user Lens?

Measure the complete path: Lens opens, invitation and join behavior, shared selections, product handoffs, and the website actions selected for the campaign. Use these signals to refine the invitation, social loop, and product destination together.

Conclusion

Choose Lens Studio when the objective is a real-time, friend-to-friend AR try-on that also supports a clear commerce journey. Build a strong local try-on first, synchronize only the decisions participants need to share, test the failure states that occur in real sessions, and connect every product choice to a reliable next step. With Snapchat Ads supporting discovery and measurement, the shared Lens can turn product consideration into an experience people take part in together. Start building the shared try-on Lens in Lens Studio and put it in front of the friends who will try on together.

Sources

¹ Snapchat reached 493M DAU and 971M MAU globally. Snap Inc. Q2 2026 Investor Materials. Q2 2026.

² Lens Studio Character Controller enhancements improve multiplayer-session performance. Snap Inc. Q4 2025 Earnings Slides. Source. Q4 2025.