← Work

Health / Fitness · Digital Product · 2023 to 2024

ZOZOFIT

An at home 3D body scanning app: multiple B2C launches, iOS subscriptions, and the flow work I did by hand before any of it reached a screen.

Role
Product Manager · Product Designer
Team
Small cross functional squad
Platform
iOS · Android · B2C
Timeline
2023 to 2024
  1. ZOZOFIT: Measure

    01Measure

  2. ZOZOFIT: Side-by-Side

    02Side-by-Side

  3. ZOZOFIT: ColorMetric

    03ColorMetric

  4. ZOZOFIT: Set a goal

    04Set a goal

One measurement does not tell you anything. The product is what comes after it: hold two scans against each other, colour the difference so it reads at a glance, and turn it into a goal.

Context

ZOZOFIT turns a home body scan into measurements tracked over time, across more than twelve locations on the body. I owned end to end product development across multiple B2C AI launches in a small squad. Most of that job was turning multi step, AI driven health data into something a person could follow on a phone.

Six ways of reading a body

  1. 01

    Measurements

    Over twelve key locations on the body, captured from a single scan.

  2. 02

    Body fat percentage

    Calculated from the scan, so the headline number comes out of the same capture as everything else.

  3. 03

    Side-by-Side

    Compare two scans to evaluate differences on a detailed view basis.

  4. 04

    ColorMetric

    Growth, reduction or no change, with colour intensity proportional to the percentage recorded.

  5. 05

    Trend Graph

    Measurement history along a trend line, to track progress over time.

  6. 06

    Goal Settings

    Goals for individual body parts or measurement points, with progress against them.

ZOZOFIT: The start scan userflow, argued out on a whiteboard. The bra
The start scan userflow, argued out on a whiteboard. The branch at the top is the one that matters: suit or no suit, because the two paths need different guidance, different accuracy expectations and different copy from the first tap.
ZOZOFIT: plate 1
ZOZOFIT: plate 2
ZOZOFIT: plate 3
ZOZOFIT: plate 4
The brainstorming behind those flows, sketched screen by screen on the wall. This is where first time versus returning scan states got settled, and where the subscription decision found a place that did not hijack the experience.

The scan was the easy part. Suit or no suit, first time or returning, subscribed or not: those branches are the product.

Subscriptions, and the review nobody schedules

I implemented RevenueCat to launch iOS in-app subscriptions, built the paywalls, ran A/B tests and analysed conversion, engagement and revenue impact.

Before submission I reviewed the paywall against Apple's subscription guidelines myself and corrected pricing disclosure, trial terms and the cancel and restore path. Those are cheap to fix in design and expensive to fix in review. A rejection there costs a release window, not engineering hours, which is why I would rather spend an afternoon on it than find out from App Review.