A design decision companion
I'm designing…
Choose what you are working on. Each view gathers the parts of the library that bear on that surface, in the order you need them: what to know, what to build, what to check.
14 surfaces
A Form
Signup, application, settings or anything else where people type things in.4 decisions · 23 resourcesA Dashboard
Analytics, monitoring or any screen whose job is to answer a question at a glance.4 decisions · 22 resourcesA Mobile App
Native or mobile web, where reach, input precision and connectivity all change.4 decisions · 22 resourcesAn Ecommerce Experience
Browsing, comparing and buying, where trust and honesty are load-bearing.4 decisions · 23 resourcesA Checkout
The last few screens, where every unnecessary decision costs a sale.4 decisions · 21 resourcesA Search Experience
The input, the suggestions, the results and everything that happens when there are none.4 decisions · 19 resourcesAn Onboarding Flow
The path from arrival to the first moment the product is actually worth something.4 decisions · 20 resourcesSettings
Preferences, account and configuration, where the defaults matter more than the controls.4 decisions · 20 resourcesNavigation
How people find out what exists and where they currently are.4 decisions · 20 resourcesA Data Table
Many records, many attributes, and comparison down a column as the actual task.4 decisions · 22 resourcesAuthentication
Sign-in, sign-up, recovery and the security decisions that show up as usability ones.4 decisions · 17 resourcesAn AI Product
Model-driven features, where explanation, control and correction carry more weight than accuracy.4 decisions · 20 resourcesAn Enterprise Workflow
Tools used all day by trained people, where efficiency beats first-use friendliness.4 decisions · 23 resourcesA Pricing Page
Comparison under uncertainty, where framing decisions are also ethical ones.4 decisions · 20 resourcesNot listed here?
These are the surfaces where the decisions are distinct enough to be worth a curated view. For anything else, search describes the problem better than a category does.
Search the Atlas