united.com
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.
- Millions
- Audience
- Ping Identity
- Auth
- WCAG 2.0
- A11y standard
The problem
Signing up is where a loyalty program gains a member or loses them on page three. It is never one form. It branches through two-factor codes, a handoff to a bank's login, and a parent approving a child's account - and every branch has to survive a refresh, a back button, and a screen reader without stranding the traveller.
What I built
One reusable passcode flow, instead of a separate modal on every page that needed one
A child's account waits on real consent from the server, never on an assumption made in the browser
Miles-to-cash conversion: pick an amount, see the real exchange, before you commit
What changed
- Used by millions of travellers
- Four years of accessibility work - focus order, screen-reader announcements - so the flow works without sight
- Two-factor contact data hardened to payment-industry standard
Stack
- React
- Redux
- Redux-Saga
- Immutable.js
- Ping Identity
- react-intl
- Accessibility (WCAG 2.0 / ADA)
- Claude Code