PRODUCT DESIGN · 2026

Swipey Admin

Proven on desktop. Unusable in a pocket.

PROBLEM_

Every admin flow already worked on desktop: deposit, top up, clawback, issue card, invite, approve. None of it was reachable from a phone. The people who needed it were away from their desks.

MY ROLE_

Design and design QA on the first admin-facing mobile release, built with AI agents and prototyped for stakeholders and an audience aged 30 to 60.

RESEARCH_

The desktop product was the research. Every rule, status and edge case already had a proven answer, so the job was translation, not invention.

Grey doesn't read as "done" to someone who's sixty. It reads as something went wrong.

KEY INSIGHT_

CHALLENGE_

Port the business rules, don't reinvent them. Writing new validation for flows that already worked would have been risk with extra steps.

PROCESS_

I reviewed it screen by screen, giving every finding a stable ID and a severity tier, and tagging the ones engineering had to build as requirements rather than visual edits.

SOLUTION_

Every admin flow on a phone, with a legibility floor, 44px targets, an AA contrast system, and one status vocabulary instead of two.

LIVE PROTOTYPE_

The working prototype is embedded below.

Sign in with any nine-digit phone number, then any six-digit code, pick a workspace and choose the Admin role. Every admin flow is clickable from there.

MOBILE PREVIEW_

Desktop-scale prototype — open on a larger screen to try it.

OPEN LIVE APP ↗

OUTCOMES_

Three blockers survived seventy-four findings of review. An audit is not the same job as a review. Next I'd test with actual sixty-year-olds instead of designing for them.

← PREV

Atom OS

Custom Fields