Skip to results

Reading paths

Curated reading paths through the TFMSTYLE UX Handbook.

Ship a form - Everything that decides whether a form gets finished or abandoned, in the order you build it.
Accessibility pass before launch - A run through the checks that catch most real barriers, ending with how to audit the whole flow.
A design system from scratch - From the first tokens to the governance that keeps a system alive after the launch team moves on.
Make it feel fast - Perceived speed is a design decision. What to load, what to fake, and what to never block on.
The states nobody designs - Empty, loading, error, offline, stale, and partial. The screens that decide whether a product feels solid.
Mobile essentials - The handful of things that separate a real mobile interface from a shrunken desktop one.
AI product surfaces - Designing for output you cannot fully predict, without pretending it is certain.
Data and dashboards - Tables, charts, and numbers people will act on, including the formatting that decides whether they act correctly.
Account, billing, and leaving - The surfaces that decide whether people trust you with a card, a team, and their data.
The first five minutes - Getting a new account from an empty screen to the moment the product is obviously worth keeping.
What the backend does to your interface - The system facts that decide what a screen has to show, in the order they tend to bite.
Ship a live screen - Everything that decides whether a real-time interface stays trustworthy when the connection does not.
When the system says no - Refusals, overload, and permanent failure, and how to make each one readable instead of alarming.
Ship a release without breaking anyone - Rollouts, skew, migrations, and removals, from the user's side of the deploy.
The security surfaces designers own - The screens where a design decision is also a security decision, and nobody else is going to make it.
Sign-in, end to end - From the first login field to revoking a session on a stolen laptop.
Search that actually finds things - Matching, ranking, and the empty states in between, including what the newer engines get wrong.
Editing together without losing work - Two people, one record, and every way a product can quietly throw one of their edits away.
Files in and files out - Uploads, exports, archives, and shared links, all of which take longer and fail more than the design assumes.