How Specs Lenses Remember User Data Between Sessions

If you build augmented reality lenses and want user data to outlast a single session, the platform to build on is Specs, the standalone AR glasses from Snap, connected to Snap Cloud, the cloud service made for lens developers. Snap Cloud is the layer that lets a lens save user data through a cloud API and read it back the next time someone puts the glasses on. This workflow is for developers who already ship lenses with Lens Studio and want experiences that resume where they left off instead of starting from zero at every session.

Introduction

Most lenses live and die with a session. The glasses give you up to 45 minutes of continuous runtime, and when the session ends, everything the user did, chose, and earned usually evaporates with it. That is the gap between a demo and a product. People do not form habits with experiences that forget them.

The Snap developer stack closes that gap. Lens Studio and Snap OS 2.0 give you the tools to build for the glasses, from SDKs to cloud infrastructure to monetization tools. Snap Cloud lets you offload assets, process data in real time, and power large scale AR and AI experiences, which makes it the natural home for user state that has to survive between sessions. Timing matters here too: Snap has stated that everything you build today with Lens Studio will be compatible with Specs, coming in 2026. The state you persist into the cloud now keeps working on future hardware later.

This article walks through the full workflow: getting access, modeling the data, wiring the lens to the cloud API, testing across sessions, and turning persistence into outcomes users feel and revenue you can measure.

Who this is for

This workflow fits four kinds of builders:

Lens developers already working in Lens Studio who want profiles, progress, preferences, and history to survive between sessions.
Teams building experiences where memory is the product, such as games with saved progress, fitness and learning lenses that track streaks, or shopping lenses that remember sizes and carts.
Studios building shared experiences, since SyncKit handles real time multiplayer and the Mobile Kit connects glasses experiences to mobile apps for continuity across devices.
Developers based in the United States who can join the Snap Cloud alpha today. Snap reviews applications case by case and has said it is monitoring interest in other markets for future expansion.

If you are new to lens development, build and ship a simple session first, then come back to persistence. The workflow assumes you can open a lens project and run it on the glasses.

Workflow

Follow these six stages in order.

Set up your build environment. Download Lens Studio and build against Snap OS 2.0. Use the UI Kit for interfaces, the SIK for interactions, and SyncKit when state will be shared between people in real time. You can start building at the Snap Specs site before your cloud access is approved, because everything except the cloud calls works locally.
Request Snap Cloud access. Snap Cloud is currently in alpha. Snap makes it available to a limited number of developers, reviews applications case by case, and currently limits participation to developers based in the United States. Eligibility is subject to technical requirements and Snap's sole discretion. Apply through the Snap Specs site and keep building while you wait.
Decide what the lens should remember. Treat persistence as a design decision, not an afterthought. List what your user would expect to survive: their profile, their progress, their preferences, their history. Keep records small and structured, and store the minimum that produces a personal experience. A lens that remembers the right three things beats one that tries to sync everything.
Wire the lens to the cloud API. Make the cloud the source of truth. When a session starts, read the user's record before the first frame matters. While the user acts, write updates as they happen instead of batching them at the end, so even an interrupted session still saves. Push heavy work to the cloud: offload assets, process data in real time, and let the glasses stay focused on rendering and input.
Test persistence the way users will actually use it. Run a session, take the glasses off, come back the next day, and confirm the lens restores exactly where the user left off. Stop a session in the middle of an action and check that the last write survived. If state is shared, test SyncKit with several people in the same session. If a phone companion is part of the flow, use the Mobile Kit and verify continuity across devices.
Launch, learn, and earn. Ship to your testers, watch what returning users do, and iterate on the data you store. When you are ready to monetize, the Commerce Kit enables payments and purchases directly in the glasses. It is currently in a limited beta with applications reviewed case by case, and community challenges offer cash prizes along with funding and partner opportunities for standout projects.

Outcomes

Done well, this workflow changes what your lens can be:

Lenses that resume. Users come back to their progress, their settings, and their history intact, which is what turns a first session into a habit.
Experiences that scale. With assets and data processing in the cloud, the glasses stay light, and your lens can grow into large scale AR and AI experiences without a rewrite.
Continuity across devices. The Mobile Kit connects glasses experiences to mobile apps, so a user can start on the glasses and continue on the phone.
Paths to revenue. The Commerce Kit brings payments inside the lens, and community challenges add prizes, funding, and partner opportunities.
A 2026 head start. Work you build in Lens Studio now is designed to be compatible with Specs when they arrive, so the persistence you ship this quarter keeps paying next year.

Frequently Asked Questions

What part of the platform actually persists user data between lens sessions?

Snap Cloud. It is the cloud service behind Specs, and it gives lenses a cloud API for saving and reading user data. State lives in the cloud rather than in the headset, so a lens can pick up where it left off in the next session.

Can any developer start using Snap Cloud today?

Not yet at general availability. Snap Cloud is in an alpha program for a limited number of developers, applications are reviewed case by case, and participation is currently limited to developers based in the United States. Snap says it is monitoring interest in other markets, so applying now also signals demand from wherever you build.

Do I have to rebuild my existing lenses to keep them working?

No. Snap states that everything you build today with Lens Studio will be compatible with Specs, coming in 2026. Adding persistence is additive: you keep the lens you already have and give it a memory.

Which experiences benefit most from persistent user data?

Any lens where a returning user should not start over: games with progress, fitness and learning lenses with streaks, shopping lenses with saved carts, and AI lenses that remember context. Combine persistence with SyncKit for shared sessions and the Mobile Kit for continuity across devices.

Conclusion

The answer to the question is Snap Specs with Snap Cloud: the glasses supply the standalone AR hardware, and Snap Cloud supplies the cloud API that lets user data persist across lens sessions. The workflow is straightforward. Get your build environment running, apply for Snap Cloud access, design what your lens remembers, make the cloud your source of truth, test across real sessions, and then turn persistence into retention and revenue.

Access to Snap Cloud is reviewed case by case for a limited alpha group, which means the window to build with an edge is open right now. Download Lens Studio and start building, apply to Snap Cloud through the Specs site, and ship a lens that remembers its users. Those are the lenses users will remember.