J.Hilburn · 2025 · iPad Redesign · Built in native iOS

Fit Survey.

A full redesign of J.Hilburn's pre-appointment client survey — a stylist's new-client onboarding flow.

And I didn't just design it. I built it in native iOS.

It's live — go ahead, tap around. Open it full screen ↗

The brief · my role

Make the intake worth finishing.

The old survey was a wall of forms and tiny pickers — everything asked at once, before an appointment could even start. I redesigned the whole flow into a calm, one-question-at-a-time experience, with illustrations and real garment photography doing the explaining.

Then I took it past the brief: I built it as a native iOS app — Figma to working Swift, via Claude Code. A rare case of a designer shipping her own work in code.

A redesigned survey step on iPad — 'How tall are you?' with a vertical ruler and feet/inches steppers

The old survey asked for everything at once. The redesign asks one question at a time.

— The redesign in one line

01 — The problem

Everything, all at once.

The old intake piled whole categories onto single screens — personal info and billing in one form, then height, weight, body shape, ethnicity and fitness level on the next, then a wall of tiny size pickers, then a long scroll of fit-preference labels. It worked, but it was a form to endure, not a conversation to have.

The old survey on iPad — one screen asking height, weight, belly shape, ethnicity and fitness level together

Old "About Andrew" — six questions on one screen.

The old survey on iPad — a dense wall of horizontal size pickers

Old "Size" — a wall of tiny pickers.

02 — The redesign

One question at a time.

Same information, completely different feel. Every dense screen became a focused step — an editorial headline, one decision, an illustration or a purpose-built control. Here's the before and after, pair by pair.

Old new-client form on iPad — one dense form

Before — one dense form, everything required-looking.

New 'Let's get started' on iPad — just the essentials, optional details in accordions

After — just the essentials; address, card, company optional.

Old measurement-capture choice on iPad — three bare cards

Before — a bare three-card choice.

New capture-measurements screen on iPad — four described options including a virtual measuring tool

After — described options, plus a new Virtual Measuring path.

One screen became six steps.

The worst offender — the screen asking six things at once — split into six single-question steps, each illustrated and unhurried.

Step — body type, five drawn figures — Body type

Step — height, a vertical ruler — Height

Labels became real garments.

The long fit-preference scroll of slim/trim/classic labels became simple visual A/B choices — the client sees two real fits and picks the one they like.

Fit preference — which shirt do you prefer, two real photos — Shirt

Fit preference — which sportcoat, two real photos — Sportcoat

Fit preference — which trouser, two real photos — Trouser

03 — A new touch

Put a face to the fit.

Net-new — no old equivalent

A camera that invites.

The redesign added an optional client-photo step the old flow never had. The camera lens is rendered as an actual viewfinder into the iPad's camera — a small, warm detail that makes adding a face feel like part of the relationship, not data entry.

The new client-photo step on iPad — a camera lens rendered as a viewfinder, headline 'Put a face to the fit'

04 — Designed and built

From Figma to Swift.

Most designers hand a redesign off and hope. I built this one. Using Claude Code, I took the survey from Figma into a working native iOS app in Swift — every step, control, and transition is running code, not a clickable mockup. Two screens were designed directly in code, never in Figma at all.

7steps

One question each

6from one

One dense screen became six

2in code

Screens designed directly in Swift

1maker

Designed and built it, Figma to Swift

06 — Reflection

What I learned.

The old survey wasn't broken — it just asked too much, too fast. The redesign's whole job was to slow it down: one question, one screen, one decision.

Building it myself changed how I design. When you know you're going to write the Swift, you stop drawing things that can't ship — and you sweat the transitions, the empty states, the keyboard, because they're yours to make work. This is the project I point to first.

IMAGINE · DESIGN · BUILD