Skip to content

Anastasiia Bondarchuk

Easy Lens Web Evolution

Easy Lens on web: a creator asks for a brighter anime effect and accepts or rejects each component change while the preview updates.

Easy Lens Web Evolution

2022–2026
Shipped0→1 platformAI-native pivot
Role
Sole designer on the web track at every stage, from the internal ML tool through V2.
Team
Product, engineering, ML and UX research
Timeline
2022–2026 · V2 launched Oct 2025
Outcome
~9.75B Lens impressions on web (as of May 2026)

A Lens is an effect you play with in the Snapchat camera, like dog ears or a new background.

Making a Snapchat Lens used to mean learning Lens Studio Desktop, a pro tool most people never got through. I took the web track from an internal ML tool only engineers could use to Snap's first LLM-powered Lens creation on the web. You describe a Lens in plain words, then keep shaping it.

The turning point was V2. We moved from templates to chat, and I designed how creators keep control of a generated Lens.

Evolution

Each stage asked less of the creator.

Over four stages, one idea held: you shouldn't need a pro tool to make a Lens.

V2: a Lens made by describing it in chat, in front of the gallery with its create bar.

Type an idea, get a Lens you can keep editing.

The pivot to chat · Oct 2025

Templates made Lenses look alike.

Why

V1 had to be template-based. At the time, it was the only way to build a Lens. A gallery review and research sessions where we watched creators build showed their Lenses were starting to look alike. Once LLMs were good enough to turn a description into a working Lens, we decided as a team to move from templates to chat.

The tradeoff

Components gave creators control and predictable results.

Generation gave range and speed, but risked a black box where you type a prompt and take what you get.

How I kept control

Every generated Lens opens as an editable component list in the chat, and edits happen on the preview. V1's generative tools moved into the same chat instead of sitting in separate panels.

The V2 platform

In V2, creation started in chat.

I designed each step: describe a Lens, refine it, publish it, then see how it does. I also designed Lens+, the Easy Lens subscription on web (shipped spring 2026): the paywall, where creators upgrade, what subscribers get, and payment details in their profile.

1 · Describe it

A creator types what they want and gets a working, editable Lens. Templates are gone. The other way in is remixing an existing Lens.

Recreated interaction, sample data.

2 · Refine it

Creators refine a Lens two ways. They ask for a change in the chat, or edit any component the AI builds by hand. They can adjust it, swap its asset or generate a new one.

Lens Components
Recreated interaction, sample data.

3 · Publish

The creator publishes the Lens from the same place they made it. Who sees a Lens is its own chapter.

Private & Targeted Publishing
Recreated interaction, sample data.

4 · Measure

Per-Lens insights are new in V2. Views, shares and rewards sit right next to publishing.

Shown with sample data.

Chapters

Explorations

Three problems I explored but didn't ship.

  1. AThread replaces chat
  2. BThread rail
  3. CSide by side
  4. DAsset view

Chat Threads

Long generations blocked the only chat, and everything had to stay on one surface. In my concept, each generation gets its own thread. I explored four versions.

Concept
  1. AComponent dropdown
  2. BAutocomplete
  3. CInline blocks
  4. DContextual pills

Dynamic Suggestions

The hardest part of an AI tool is the blank input. I explored four versions of in-context suggestions that help you build a good prompt.

Concept

Canvas

Creating isn't linear. A chat is. Canvas starts from the Sketch to Lens drawing layer, which shipped, and turns it into a board. You sketch an asset, drop in references, mark them up and compose the Lens. It's an extra mode that works alongside chat.

Conceptself-initiated

Branches

The web track didn't stay on the web.

Pros got the same ML models in Lens Studio Desktop, and V2 brought chat creation to phones. I designed the desktop plugins and continued the mobile work.

Generative Plugins

Six ML and generative tools inside Lens Studio Desktop, most of them on one shared design template. Built for expert creators.

ShippedPro-tool AIshared design template

Easy Lens Mobile Redesign

Creation on mobile was a bar people didn't notice. I gave it its own place, then designed how creators edit there.

Shipped after I leftResearch → shipped iteration

Impact and scope

What changed for creators, and how far it reached.

FeatureBeforeAfter
Lens ComponentsType a prompt, take what you getEvery generated Lens opens as editable components
Version ControlEach AI edit overwrote the last oneEvery meaningful edit is a named version you can restore
Chat DraftsStarting a new Lens meant losing the last oneEvery chat is a saved draft you can resume
Private publishingPublic to everyone, or nowherePublic or Private, shared by link or Snapcode
Cumulative Lens impressions on web
04B8B12BLSW V1 · JUN 2025LSW V2 · OCT 2025MAY 2025JULSEPNOVJAN 2026MARMAYAUG 2025~1.02BJAN 2026~6.19BMAY 2026~9.75B04B8B12BLSW V1JUN 2025LSW V2OCT 2025MAY 2025SEPJAN 2026MAYAUG 2025~1.02BJAN 2026~6.19BMAY 2026~9.75B

Cumulative web impressions grew from ~1.02B in Aug 2025 to ~6.19B in Jan 2026 and ~9.75B in May 2026. V2 launched in Oct 2025.

Creation funnel
Opened100%
Started creating~83%
Submitted a Lens~23%

Of people who opened Easy Lens on web, ~83% started creating and ~23% submitted a Lens

Reflection

Control is the product.

Chat made it easier to start, but generation alone would have been a demo. Easy Lens became a tool because of what came after the first prompt: components, versions and drafts that kept the creator in control. That's how I approach AI-native products now. The first generation is a starting point, and the real work is everything after it.