Passion Nails

Passion Nails is my mom's nail salon in East York, Toronto. I designed and built its booking site and a staff app in Vietnamese, and the salon has run on them every day since November 9.

Role
Design engineer: research, design, design system, build, launch
Team
Me, with my mom June (the owner) and the techs Kim, Dina and Alex
Timeline
November 2026, live since November 9
Scope
Booking site, Vietnamese staff app, design system, texts and push
Outcome
Used daily; about 4 hours a week back for my mom
Live site
0:00 / 0:00

The problem

Every booking was a phone call my mom took mid-manicure.

One phone, no front desk, and she picks up between customers and during them. In January she leaves for Vietnam, and the techs will have nobody to ask.

people at the front desk.
customers on a usual day, each one a call.
techs, most over 40, who read Vietnamese first.

Research

I asked 59 questions before writing any code.

Each one a real choice with its trade-offs written out, for my mom to pick. 32 more came once the techs had it in their hands. Three answers that shaped everything:

I don't like the text code to verify, because that's just extra inconvenience for most customers.
On fake bookings
I also don't want to do limits like that, in case it's a mother and her daughter going.
On limits per phone number
Can we do a push notification every time someone cancels?
On what she needs to know
My mom, in our planning answers.

Research

Then I held the first build the way an older tech would.

Vietnamese on, a small phone, reading glasses in mind. I found 13 places she'd get stuck, three of them on the first screen.

First build

9:41
The first build's day view in Vietnamese, with English day letters and a floating plus button
  1. English inside the Vietnamese

    Days read S, M, T, W. Dates read 'Wed Nov 11'.

  2. A tech cut off

    The filter ran off the edge, so Alex wasn't on screen at all.

  3. A plus with no word

    No label, and it sat on top of the last appointment.

The first build, the way a tech first saw it.

Insight #1

One wrong tap could close the salon.

Opening hours opened with 'Closed' already ticked for today. One tap on Save, and online booking stops with nobody knowing why.

First build

9:41
The first build's opening hours: today's date with Closed already ticked
Đóng cửa (Closed), ticked by default.

Insight #2

Half-translated reads as untranslated.

Buttons were Vietnamese, but days and dates stayed English. And the words were Southern, in a salon that talks the Hanoi way.

  • Late

    First build (Southern)
    trễ (late)
    Now (Hanoi)
    muộn (late)
  • Move

    First build (Southern)
    dời (move)
    Now (Hanoi)
    chuyển (move)
  • Wednesday 11

    First build (Southern)
    W 11
    Now (Hanoi)
    T4 11 (Wednesday 11)
What a stranger would write, and what the techs say.

The opportunity

So I set myself one question.

How might four techs run the salon from their phones, in their own words, with nobody to ask?

Design decision

Vietnamese by default, the way the techs actually talk.

The first build was machine-translated, so it came out Southern. Walking the techs through the real app, again and again, gave me their words: muộn (late), not trễ (late). Nail words like manicure, shellac and fill stay English in both languages, because that's what everyone says at work.

Today's appointments in Vietnamese
9:41
An appointment in Vietnamese with labelled minute buttons
9:41

Khách đến muộn (Customer running late), +5 phút (minutes), and T2 (Monday) to CN (Sunday) for the days.

Design decision

What the techs tap all day beats Apple's and Google's minimums.

Most of the techs are over 40 and immigrants, and still fairly new to smartphones. So their app gets bigger controls than the customer site: chips went from 40 to 50 px, buttons to 54, and every minute button says phút (minutes), so +5 is never a guess.

  • Today button

    first build

    36
  • Staff filter chips

    first build

    40
  • Apple's minimum

    44 by 44 pt. Apple HIG

    44
  • Android's minimum

    48 by 48 dp. Android Accessibility Help

    48
  • Staff filter chips

    now

    50
  • Buttons

    now

    54
0204060 px
Control heights, from the app's own styles.

Design decision

A walk-in tells you who's free before you save.

Add sits in the bottom bar, where it can't cover an appointment. Big wheels replaced the phone's tiny English date picker, and a green line says who's free before anyone taps Lưu (Save).

9:41
0:00 / 0:00
Adding a walk-in, in Vietnamese.

Design decision

'Any staff' goes to whoever has the least chair time.

The techs are paid per service, and customers ask for June and Kim by name. So 'Any' goes to the tech with the fewest booked minutes, and the customer is promised the slowest tech's finish time, so a swap never makes them late.

A customer picks Any staff
Techs who are free thenand who do that service
Fewest booked minutes todayties go Dina, Alex, Kim, June
The customer sees a 'done by' timefrom the slowest tech who could do it
The day uses the real tech's timeplus the gap, so no minutes go to waste
Fair for the techs, and June is still free for the people who ask for her.

Design decision

Booking is four steps, with no account and no code.

Hands, feet and combos, one of each. The site remembers you on your own phone. A text code only shows up for something odd, like a fourth booking on one number, so a mom and daughter never see one.

9:41
0:00 / 0:00
A returning customer books a pedicure.

Design decision

Every text fits in one SMS.

Carriers charge for every text, so I priced the providers all-in and picked Telnyx. Messages stay under 160 plain characters (one emoji can triple the cost), and the 9:30 reminder skips anyone who just booked or added it to their calendar.

  • Twilio

    2.3¢
  • Plivo

    2.4¢
  • Telnyx

    the one I picked

    1.7¢
0123 ¢
My all-in estimate per text, carrier fees included: about C$20 to C$31 a month.

Explorations

I said no to a text code on every booking.

It taxes every customer to stop a rare few. Three ways to stop fake bookings, side by side:

  • A code on every booking

    • + Proves the number is real
    • − An extra step for every customer
    • − One more paid text per booking
  • A limit per phone number

    • + No extra step
    • − Blocks a mom and daughter booking together
  • Invisible layers first

    • + A bot check, a hidden field and rate limits nobody sees
    • + Staff can block a number
    • + A code only at a fourth upcoming booking
    • − More to build

    The one we built

Design system

One design system, and both apps use all of it.

The staff app used to look different, and when I checked why, there was no good reason. I'd cut the site's fonts to English letters to load fast, then given the staff app the phone's font instead. Now both apps share every colour, font and shape, and Vietnamese letters load only where they're needed.

Colour

Five roles. Burgundy only marks what's chosen or new.

  • Cream

    #f4ebdf · the page

  • Card

    #fbf7f1 · cards and sheets

  • Ink

    #0e0e0e · text and hairlines

  • Burgundy

    #87133e · chosen, new, Add

  • Line

    #8c7b68 · control edges, 3.4:1

Type

Two faces in both apps. Vietnamese letters come in a 9 KB cut, loaded only where they're needed.

Passion Nails

Zalando Sans Expanded · display

Khách đến muộn

Hanken Grotesk · text, 17 px for staff

Thêm lịch hẹn

The site's Latin cut: the burgundy letters aren't in it.

Thêm lịch hẹn

With the Vietnamese cut, in both apps.

Shape

What you read is square. What you tap is round.

  • 11:00am Maria SantosPedicure & Manicure Shellac

    Cards, sheets, notices

    0 px and an ink hairline, like the site's reviews.

  • Gọi+5 phút

    Buttons and chips

    Fully round. 54 px tall in the staff app.

  • Khách walk-in

    Fields and tiles

    12 px, for controls too tall to be pills.

Components

Every size is a token. In the staff app, nothing you tap is under 48 px.

Button

54 high, sides 1.6em

Lưu lịch hẹn
Lưu lịch hẹn

Chip

50 high, 8 from dot to name

June
June

Field

50 high, 12 corners

Khách walk-in
Khách walk-in

Appointment card

12 inside, square

10:00am10:35amLinh TranPedicureJune
10:00am10:35amLinh TranPedicureJune

Spacing

A 4 px grid from 4 to 32. Inside a card, 12; between the fields of a form, 16.

  • 4spacing-1
  • 8spacing-2
  • 12spacing-3
  • 16spacing-4
  • 20spacing-5
  • 24spacing-6
  • 32spacing-8

Design system

Side by side, the staff app is just bigger.

The staff theme sets three things: 17 px text, 48 px+ targets, and buttons in sentence case, because capitals crowd Vietnamese tone marks. Everything else comes from the site, down to the reviews' square cards.

The same components in both themes: buttons, a segmented control, time chips, a service card, a field, badges, notices and a card
Same components, same tokens: the site on the left, the staff app on the right.

Final solution

Turn the phone sideways, and the whole salon's day fits.

Both apps share one schedule, so a booking made at midnight is on every tech's phone by morning, and the 9:30 reminder goes out on its own.

0:00 / 0:00
A usual day, by tech: about 30 customers.

Outcome

It's live, and my mom gets about four hours a week back.

That's her estimate of the calls, the texting back and forth, and copying each booking into her book for the techs. Over five years, it adds up:

hours back, at four a week.
eight-hour days off the phone.
to pay someone for those hours at Ontario's minimum wage of $17.95, before payroll costs. Ontario

Looking back

I'd put a phone in a tech's hands on day one.

The first build passed every test and still had 13 places a tech would get stuck. Five minutes on a phone, in Vietnamese, found them.

What the tests caught

  • Two people booking the same slot at once
  • A text running past 160 characters
  • A reminder sent twice

What only a phone in Vietnamese caught

  • 'Closed' ticked by default
  • June picked for every phone at login
  • A tech cut off the screen

Key learnings

I learned that the hardest user decides the design.

  • Design for the hardest user. Booking was easy; a tech in her second language, with a customer in the chair, set the bar.
  • Defaults are decisions. A pre-ticked box and a pre-picked name were the two most dangerous things in the first build.
  • Ask why twice. The staff app's second look came from a shortcut I'd forgotten, not a reason.

This is a snapshot of the process. Ask me for the full story.

say hi