Back to work
Zaps · Turnip · 2024–2026

I designed the Zaps creation experience that grew revenue 7.5x

Zaps helps everyday creators make posts, stories, reels and carousels that look professionally designed. The app changed direction three times while I was there, and I designed how it is used through all of it.

A screen from the Zaps editorA screen from the Zaps editorA screen from the Zaps editorA screen from the Zaps editorA screen from the Zaps editorA screen from the Zaps editorA screen from the Zaps editorA screen from the Zaps editorA screen from the Zaps editorA screen from the Zaps editorA screen from the Zaps editorA screen from the Zaps editorA screen from the Zaps editorA screen from the Zaps editorA screen from the Zaps editor
A hand holding a phone running the Zaps app
TL;DR

Users come to Zaps to make stunning content, fast. I designed the experience for it end-to-end; the tools to make and edit content, the 5,000+ ready-made templates they start from, and how they share it with the world. In the six months after the new experience launched, revenue grew 7.5x.

7.5x
more revenue
12x
more paying users
6x
more users overall

Measured from our own paywall data, in the six months after launch and before we spent heavily on marketing.

My role

What I did

Research
Designed the experience
Led the template team
Testing
Engineering handoff

Across every version of the app, I designed how it is used, from talking to creators and researching, to designing the screens, testing them, and handing them to engineers to build. The direction and business calls sat with our design lead and the product and growth teams.

Research

I designed around real users

Our users post every day, but they are not designers. So before designing anything, I did my research:

01

I studied 20+ apps to build on habits users already had

I looked at how more than 20 popular editing apps work. Building on things users already knew from other apps meant they could pick up Zaps right away, instead of learning it from scratch.

02

I listened to the creators who use Zaps every day

I talked to creators, watched how they made their posts, and asked what got in their way. When they told us something was hard, we fixed it and shipped the change.

03

Some users browse, some search, so I designed for both

Some users open the app just to look around for ideas. Others come in knowing exactly what they want. I also studied what makes a user pick one template over another, so both kinds could find something fast.

04

A tool should only be as deep as it needs to be

A simple thing like adding a filter should stay one tap away, not buried under menus. A tool that does a lot, like adjusting light and color, can open up more. When how deep a tool goes matches how much it does, users never get lost.

Research board covering filter and template-creation flows, competitor apps studied, module navigation depth, and the reusable UX patterns drawn from them

Research board, the users we designed for and how they create

The problem

Zaps had changed so much, it no longer felt like one app

Zaps did not start as a creator tool. It began as a social app for a young, Gen Z crowd, then kept changing as we tried new ideas, until it became a creation app for a more grown-up group of creators. Every change added features fast, but no one stepped back to make them fit together. The app worked, but it felt like a few different apps stuck under one icon.

01

Every format worked differently

Making a post, a story, a reel, or a carousel each worked its own way. A user who figured out one still had to learn the next from scratch.

02

No two tools behaved the same

Each tool opened, confirmed, and closed differently. Nothing was predictable, so a user could never settle into a habit and just create.

03

Too many options at once

Tapping a tool put every setting on screen at the same time. It was a lot to take in, and it made simply getting started feel harder than it should.

V1: Zaps as a photo-first social app — real-time camera replies with text and stickers

V1 — a social app for real-time photo replies

V2: Zaps as an AI editor — outfit try-ons, AI hairstyles, and an enhance before/after

V2 — an AI editor for outfits, hairstyles, filters

V3: Zaps as a template-based creator tool — wallpapers, birthdays, love collages, and viral story ideas

V3 — a template-based creator tool (current)

Problem statement

As Zaps grew from a social app into a creator tool, its editing experience became fragmented. The challenge was to bring every format and every tool into one experience that feels like a single app. The goal was to make creating content fast and familiar, so more users finish what they start and keep coming back.

What I designed

One smooth path from idea to posted

I brought the whole thing together, so making anything on Zaps works the same way and feels like one app.

01

Find

Browse or search 5,000+ ready-made templates, or start from your own photo. Built to work whether you're exploring for ideas or you already know what you want.

02

Make

The same tools, text, stickers, filters, frames, work the same way for posts, stories, reels and carousels. Complex tools opened with progressive disclosure.

03

Share

Post straight to Instagram or TikTok. For reels, I designed how licensed music gets added the right way, so posts don't end up muted.

The unified experience, the same tools across every format
Testing & feedback

We listened, watched, and fixed

Feedback from creators and how users actually used the app decided what we changed. Two examples:

Stickers

Users couldn't find the right sticker

As we added hundreds of stickers, creators told us they couldn't find the one they wanted. So I rebuilt how stickers and frames work.

Templates

Users wanted to try another template

Once they had started, users told us that switching to a different template meant going all the way back to the gallery and starting over.

What we built from that

Two fixes, both built to scale

Stickers & Frames

Stickers that stay easy to find

Grouped into packs, with recently used and search up front, so the library stays quick to use even with thousands of stickers.

Templates

Switch templates without starting over

A user can swap to a new template from inside the editor, keeping the photos and text they already added.

Sticker search and category browsing, a recently-used row, and a sticker placed on a photo

The rebuilt sticker library — packs, search, and recently used, all up front.

Switching templates from inside the editor — browsing another template and applying it without losing existing edits

Switching templates from inside the editor — the photos already added carry over.

The templates

The ready to use templates users start from

Most users don't start from a blank screen, they pick a template and make it their own. I built the library of these, and led the team behind it.

Led a team of 10
5,000+ templates
6x faster to make
01

I set up how templates are made

Wrote the rules for building them so the engineering team could turn a designer file into something users can actually edit in the app.

02

I hired and led the team

Ran a team of 8-10 freelance designers and mentored a junior designer directly. Together we made 5,000+ templates, the ones the app earns from.

03

I made them 6x faster to build

I proposed to put together a shared kit of frames, stickers and fonts, cutting the time to make one template from 30 minutes to 5.

The Zaps App Store listing — icon, title and five screenshots covering carousels, reels, templates, frames and stickers

App Store screens I worked on.

What I learned

Build it to evolve, because it will

Zaps changed direction three times. What made the difference was not moving fast; it was designing the app so each new change could build on the last one, instead of starting over every time.

Next projectThe Zaps design system

Zaps · Turnip, Product design by Pranjali · 2024–2026