top of page

SmugMug · iOS Consumer Experiment

I led the product design of SmugMug’s iOS Personal Plan experiment, simplifying onboarding, navigation, sharing, and privacy for everyday photo keepers while helping the team test whether SmugMug could serve a new consumer segment.

User Research

ROLE

Lead Product Designer · 

TOOLS USED

Figma | Miro | Google Suite​

PLATFORM

iOS + shared-gallery mobile web experience

TEAM

Product | Research | Engineering | Marketing | Operations

TIMELINE
2026​

SCOPE
Zero-to-one | Consumer growth | Onboarding | Sharing | Privacy

IMPACT

17% Trial-to-paid conversion in month 1 · 11 - 2 Onboarding questions · 6 - 4 Steps in the core Library-to-Gallery sharing flow

f7a7faeb-a76c-49aa-9877-aeabbb238631.png
screenshot.png
IMG_1135.PNG
IMG_1152.PNG

The Opportunity

SmugMug was designed for photographers. Keep was for everyone else.

SmugMug’s existing mobile experience was built around photographers, selling, galleries, and professional workflows.

​

The Personal Plan experiment targeted a different audience: everyday photo keepers who wanted to store, organize, back up, and share personal photos with family and friends.

​

That meant the challenge wasn’t simply adding a lower-priced plan. The experience itself needed to feel appropriate for a different mental model.

compare.png

The Problem

The existing product was sending the wrong signals

Early research showed that participants could understand SmugMug as a place to store and share photos, but the product repeatedly signaled “professional photographer” instead of “personal photo app.”

​​Participants struggled with:

  • the difference between Library and Galleries

  • a Sharing tab that did not behave like they expected

  • sales and professional terminology

  • a sharing paywall that created a dead end

  • uncertainty around where uploaded photos actually lived The watch-party summary captured the main product issues clearly: Library/Gallery confusion persisted, Sharing and Selling created confusion, and the Keep sharing paywall needed to be removed.

The watch-party summary captured the main product issues clearly: Library/Gallery confusion persisted, Sharing and Selling created confusion, and the Keep sharing paywall needed to be removed.

Screenshot 2026-10-02 at 12.04.16 AM.png

What we heard:

​

Library vs. Galleries felt unclear
Users weren’t sure where photos lived versus where they were shared.

​

Sharing didn’t match expectations
People expected contacts or direct sharing, not a social-style model.

​

Pro features sent the wrong signal
Sales language made Keep feel designed for photographers, not everyday users.

​

Unlimited storage resonated
Storage and backup were among the clearest reasons the product felt valuable.

Research Approach

I used research to separate product friction from positioning friction

The first study tested the existing Keep experience with iPhone users who regularly took and shared photos and were open to paying for photo storage.

​

The later round expanded beyond one-off sharing to test whether Keep’s actual value proposition resonated with the people it was built for: people managing and sharing family photo histories over time.

The follow-up research specifically explored:

​

  • current storage and sharing behavior

  • willingness to pay

  • ongoing family sharing

  • Library vs. Galleries at different levels of content

  • Auto Upload

  • print purchasing

  • whether the overall feature set fit the intended audience

research flow.png

Decision 1 — Simplify onboarding

I reduced onboarding around the user’s actual intent

The existing onboarding experience asked questions oriented toward photographers and selling workflows.

​

For Personal users, those questions were irrelevant and risked signaling that the product wasn’t built for them.

​

I explored several onboarding directions before converging on a simpler experience that identified whether someone wanted to:

  • run a photography business

  • or save and share personal photos

​

This reduced the amount of irrelevant decision-making before users could reach the product.

​

The internal exploration compared multiple onboarding options and explicitly identified the benefit of replacing several irrelevant steps with one clear intent question and a shorter route to Library.

Current onboarding.png

Before

Proposed Onbaording survey.png

After

Decision 2 — Make Library the home

I made Library the starting point for personal photo management

Research showed users consistently understood Library as the place where their photos live, while Galleries were interpreted more like folders, albums, or shared collections.

​

So the Personal experience adopted a Library-first model.

​

Users landed in Library, where:

  • uploaded photos stayed private

  • add Photos became the primary action

  • auto Upload was surfaced as a secondary path

  • galleries became the place to organize and share a set of photos

​

This aligned the experience with the way participants already thought about their photo collections.

screenshot.png

Library = all my photos

IMG_3133.PNG

Gallery = a set I organize and share

Decision 3 — Remove professional complexity

I stripped away features that didn’t belong in a personal-photo experience

The Personal Plan didn’t need the full set of controls designed for photographers and businesses.

​

I simplified the experience by removing or hiding:

  • Sales

  • Sharing tab

  • public gallery visibility

  • advanced gallery access controls

  • professional viewing tools

  • advanced gallery options not relevant to the persona

​

Gallery settings were reduced to the controls that mattered most for personal use:

  • Gallery name

  • Visibility

  • Password

  • Password hint

  • Gallery feature image

​

The goal was not to remove power arbitrarily, but to reduce decisions that didn’t support the plan’s core value.

Before

IMG_3134 2.PNG

After

IMG_3135.PNG

Changes we made:

​

  • Public access removed

  • Access controls simplified

  • Privacy language rewritten

Decision 4 — Make sharing private by default

I redesigned sharing around trust, not configuration

For Personal users, sharing needed to feel safe without requiring them to understand product terms like Unlisted or configure a long list of settings.

​

I kept photos private in Library and introduced privacy at the moment a user decided to share.

​

For the first share, users:

  • start from a gallery

  • set a password

  • then use the native iOS share sheet

  • ​

For later shares, the gallery remains protected, so the flow becomes much lighter.

​

First share = establish privacy
Later share = share quickly

Repeat Share

IMG_1152.PNG
IMG_1153.PNG
IMG_1154.PNG

1. Open the gallery

Users return to the gallery they want to share.

2. Continue to share
Because password protection is already in place, users don’t need to repeat setup.

3. Share again
The iOS share sheet opens immediately, making repeat sharing much faster.

Decision 5 — Simplify the recipient experience too

The experience didn’t stop at the iOS app

The person receiving a shared gallery might open it on mobile or desktop, so the viewer experience had to feel equally simple.

​

I evaluated SmugMug’s existing site templates and selected Zoe as the best fit because it was lighter, simpler, and easier to strip down for personal sharing.

​

For the Personal gallery experience, I removed:

  • site name

  • navigation

  • breadcrumbs

​

And retained:

  • gallery name

  • photo grid

  • share

  • slideshow

  • download

  • buy

​

The result was a gallery that felt like a shared photo experience, not a website.

IMG_3307.PNG
IMG_3308.PNG
IMG_3310.PNG
IMG_3311.PNG
IMG_3312.PNG
IMG_3313.PNG

Audit of current templates

Screenshot 2026-10-06 at 12.52.32 AM.png

Validation

We tested whether the product worked—not just whether the screens were usable

The second research round went beyond checking whether people could complete tasks.

​

It asked whether Keep’s overall proposition made sense for the intended audience.

The study compared:

​

  • a fresh account with no history

  • a seeded account with an established photo library

​

This let us observe both:

  • day-one comprehension

  • and longer-term use

​

The research questions focused on whether people understood Library vs. Galleries, how they expected ongoing sharing to work, whether Auto Upload mattered, and whether the feature set justified the price.

What changed because of research

Research directly changed the product

Sharing Paywall

  • Finding: users hit a dead end

  • Change: removed the sharing restriction for Keep

​

Navigation

  • Finding: Sharing and Sales confused personal users

  • Change: removed irrelevant tabs

​

Library vs. Galleries

  • Finding: mental model remained unclear

  • Change: Library-first apporach + improved empty states

​

Value Proposition

  • Finding: unlimited storage consistently resonated

  • Change: made storage and backup more central to Keep's positioning

​

The research summary explicitly links these findings to product decisions.

Final experience

We tested whether the product worked—not just whether the screens were usable

Q1 - Selected State.png
Q2 - Selected State.png

Onboarding

​

Two questions to route users toward the right plan.

screenshot.png
IMG_3323.PNG

Library

​

A private home for all uploaded photos.

IMG_3324.PNG
IMG_1135.PNG

Gallery Creation

​

A simple way to organize and share sets of photos.

IMG_1152.PNG
IMG_3325.PNG

First and Second Share

​​

Password protection introduced at the point of sharing.

A lighter flow once privacy is already established.

​

IMG_3311.PNG
IMG_3312.PNG

Shared Gallery​​

​

A stripped-down gallery experience for friends and family.

​

​

The complete workflow

iOS Personal Plan Experiment 2.jpg

Impact

17%

Trial-to-paid conversion in month one

​

11 → 2

Onboarding questions

​

6 → 4

Steps in the core Library-to-Gallery sharing flow

A clearer consumer proposition
Removed professional and sales-oriented friction from the Personal experience.

 

Faster time to value

Reduced the amount of work users had to do before reaching storage and sharing.

​

A stronger learning loop
Combined product analytics and iterative research to inform whether SmugMug should continue investing in the consumer segment.

Reflection

What I learned

This project reinforced that serving a new audience requires more than changing pricing or adding a plan.

​

The existing product carried years of assumptions about professional photographers. The most important work was deciding which of those assumptions still belonged and which ones needed to disappear.

​

The strongest direction came from simplifying the product around a small set of core behaviors: store, organize, back up, and share.

LET'S CONNECT :)

​

Thank you for making it all the way down here! Insider tip: my name is pronounced as "May-Tree-Yee" :)

​

I'm exploring Senior Product Designer opportunities where I can work on complex consumer products, platform experiences, and emerging AI-enabled workflows. 

​

Let's chat! You can contact me at: maitreyeemuley1491@gmail.com

​

All rights reserved       2026 Maitreyee Muley 

2212-copyright-sign.png
bottom of page