Selected work
Four systems built inside organisations at scale, and two products shipped end to end alone. Every one has a case study covering the problem, the architecture, and what actually changed.
The sign-up and sign-in behind united.com
If you've joined MileagePlus or signed into united.com, you've used this. Four years on the account surface: one-time passcodes, two-factor sign-in, federated login with Chase - and the parental-consent flow US law requires before a child can hold an account.
Read the case study
Change one value, over 200+ components repaint
United's design system - had design tokens, but components still hard-coded their own colors and spacing, so a brand change meant editing them one at a time. I rebuilt it as layers. The brand now changes in one place, and theming is a swap rather than a second stylesheet.
Read the case study
Teaching AI assistants to use a over 200 component design system
Ask an AI to build a screen with your design system and it confidently invents prop names that don't exist - so you spend the morning repairing generated code instead of writing it. This server hands the assistant the real contracts for over 200 components. The guessing stops.
Read the case study
A marketplace that peaked above $10M in NFT volume
Co-built the Skeleton UI design system and the Next.js marketplace views for Dapper Labs' NFL All Day, including the live drop queues that had to stay deterministic while thousands of people hit the same release.
Read the case study
Designed, built, and operated alone - which is a different claim from building inside a team, so they are listed separately.
Revenue-generating SaaS ticketing and storefront platform
Event ticketing and a storefront for organisers, built end to end: multi-currency Stripe payouts, cryptographically signed QR tickets, and real-time analytics for whoever is working the door.
Read the case study
SEO meta-tag auditor with live Open Graph preview
A full-stack auditor that scrapes a page server-side and renders exactly what Google, Slack, and iMessage will show for it - the preview is generated from the real DOM, not from what the tags claim.
Read the case study