📖 Book
✓ Link checked
Paid
Beginner
Why we picked it
The most accessible, practical intro to usability ever written, you can read it in a weekend and immediately fix your product. The definition of 'make it obvious, not clever.'
From
sensible.com
by Steve Krug
~200 pages
- Self-evident design is the goal, kill anything that adds thinking.
- Users satisfice: they scan and click the first reasonable option.
- Cheap, frequent usability testing beats large formal studies.
Open
sensible.com →
📖 Book
✓ Link checked
Paid
Beginner
Why we picked it
The foundational text on human-centered design that every product person should read once. It rewires how you see every product, including your own.
From
jnd.org / Basic Books
by Don Norman
~350 pages
- Make affordances and signifiers obvious, users shouldn't guess.
- Give clear, immediate feedback for every action.
- Design out errors rather than blaming users ('human error' is usually design error).
Open
jnd.org →
📖 Book
✓ Link checked
Paid
Beginner
Why we picked it
Design tactics written specifically for developers and non-designers who need to ship good-looking UI without a design background. The most practical 'make it not ugly' resource there is.
From
refactoringui.com
by Adam Wathan & Steve Schoger
~250 pages
- Use spacing, hierarchy, and font weight, not just color, for visual hierarchy.
- Start with too much whitespace, then remove.
- Design in grayscale first to nail hierarchy before adding color.
Open
refactoringui.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
The single most-cited usability framework in the field, from the definitive UX research authority. A checklist you can hold your product up against this afternoon.
From
Nielsen Norman Group
by Jakob Nielsen
~15 min read
- Visibility of system status, always tell users what's happening.
- Match the real world, use the user's language and mental models.
- Prevent errors, and make consistency and standards the default.
Open
nngroup.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
Human short term memory is tiny, so making people remember things across screens is a hidden tax on your product. This explains why showing options beats making users recall them, with examples like visible menus over blank command lines. A concrete lens for reducing the thinking a user has to do.
From
Nielsen Norman Group
by Raluca Budiu
7 min read
- Recognition is easy, recall is hard, so keep options visible
- Do not make users remember information from a previous screen
- Context and cues help users retrieve what they need
Open
nngroup.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
The practical answer to a crowded screen: show the few things most people need first, and tuck the advanced options behind a click. This one technique reduces the thinking a user has to do and lowers error rates without cutting features. Useful the moment your product grows past a simple form.
From
Nielsen Norman Group
by Jakob Nielsen
8 min read
- Show common options first, hide rare ones until asked
- This helps beginners focus and saves experts scanning time
- It resolves the tension between power and simplicity
Open
nngroup.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
A pointed case study in obvious labels over clever ones. A vague "Get Started" button reads as friendly but leaves people unsure what happens next, so they hesitate. It shows how naming the actual outcome on a button raises both confidence and clicks.
From
Nielsen Norman Group
by Aurora Harley and Kim Flaherty
~6 min read
- Label buttons with the outcome, so a person knows what happens before clicking.
- Generic calls to action lower information scent and create hesitation.
- Specific verbs beat friendly filler on every primary action.
Open
nngroup.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Concrete rules for writing the words on your buttons and menus so nobody has to decode them. It covers using a verb plus a noun (Delete Folder, not just Delete) so a label makes sense on its own. Small change, big drop in second guessing.
From
Nielsen Norman Group
by Anna Kaley
~9 min read
- Add a noun after the verb so a label makes sense out of context.
- Keep command names consistent across the whole product.
- Write for the person's task, not the system's internal wording.
Open
nngroup.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Eye tracking evidence for how people actually scan a screen, which tells you where to put the things that matter. If your important label or action sits where nobody looks, it may as well be invisible. Use this to place headings and primary actions along the path the eye already travels.
From
Nielsen Norman Group
by Kara Pernice
~12 min read
- People scan in a rough F shape, so front load key words in headings and first lines.
- The starts of lines on the left get the most attention.
- Strong visual hierarchy lets people scan instead of reading every word.
Open
nngroup.com →
✍️ Essay
✓ Link checked
Free
Beginner
Why we picked it
This is the one principle that answers your worry head on: users spend most of their time on other apps, so they expect yours to work the way those do. It names why familiarity is a feature, not laziness, and where the mental models your users already carry come from. Treat it as the case for copying on purpose, then read the counterpoint below for where copying stops paying off.
From
Laws of UX
by Jon Yablonski (principle by Jakob Nielsen)
5 min read
- Users build expectations from every other app they use, then bring those expectations to yours, so matching known patterns lowers the effort to learn your product.
- Copying a convention is not unoriginal, it frees the user to focus on the task instead of decoding your interface.
- The familiarity that helps is external consistency (matching the wider category), not just internal consistency inside your own app.
Open
lawsofux.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
This is Google's own field research on building for people coming online in markets like India, and it names the exact constraints you are up against: a 40 to 60 dollar phone with 512MB of RAM, a network that flips between 3G, 2G and nothing, and 250MB of prepaid data for the whole month. It is the clearest single primer on why a metro-built app breaks for a first-time user, and it stays concrete instead of preaching. Read it as a starting point for how you scope features, not as a checklist to blindly copy.
From
Google Design
by Google Design (Next Billion Users team)
~12 min read
- Assume slow or intermittent connectivity as the default state, not the exception: design offline-first and let the app degrade gracefully when the network drops.
- Data is expensive and rationed, so every megabyte you ship (heavy images, autoplay, background sync) is a real cost the user notices.
- Many users are new to touchscreens and English, so patterns you take for granted (swipe, hamburger menus, English CTAs) need rethinking for people building outside the big startup hubs.
Open
design.google →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
A crisp, visual reference of the psychology principles behind good UX, perfect for a founder who wants the 'why' without a design degree. Bookmark it and consult it while you build.
From
lawsofux.com
by Jon Yablonski
reference site
- Hick's Law, more choices increase decision time; reduce options.
- Fitts's Law, make important targets large and close.
- Jakob's Law, users expect your product to work like the ones they already use.
Open
lawsofux.com →
✍️ Essay
✓ Link checked
Free
Intermediate
Why we picked it
Norman's own short essay on the idea that decides whether a control looks usable: affordances and signifiers. It is the crisp, free version of why a button should look pressable and a label should say what it does. Straight from the source, and it upgrades how you talk about your own screens.
From
Don Norman (jnd.org)
by Don Norman
~10 min read
- Affordances are what an element lets you do; signifiers are the cues that reveal it.
- Signifiers matter more to designers, because they are what people actually perceive.
- Make the possible actions visible, and the screen stops needing explanation.
Open
jnd.org →
Why we picked it
Forms are where most products lose users, whether it is signup, checkout, or onboarding. This is the definitive guide to label placement, error handling, inline validation, and cutting fields you do not need. If your funnel dies at a form, the fix is almost certainly in here.
From
Luke Wroblewski (Rosenfeld Media)
by Luke Wroblewski
~226 pages
- Cut every field you do not truly need to reduce abandonment
- Place labels and validation where they cut thinking, not add it
- Show errors clearly and in context, next to the field
Open
rosenfeldmedia.com →
✍️ Essay
Free
Intermediate
Why we picked it
A former Facebook design VP walks through how to look at a screen and judge whether it works, from first impression to first use to weeks in. It gives you the questions to ask so you can critique your own designs before users do. Learning to critique is how you stop shipping screens that make people think.
From
Julie Zhuo (The Year of the Looking Glass)
by Julie Zhuo
~12 min read
- Judge a screen against what the user is actually trying to do, not your intent.
- Separate first impression, first use, and long term to surface different problems.
- Good critique is a repeatable habit, not a one off review.
Open
medium.com →
