Adam Silver
@adamsilverhq.bsky.social
Designer with engineering background. I talk about designing products that are intuitive, accessible and delightful to use.
Design newsletter:
https://adamsilver.io/newsletter
Good Design Crash Course (free):
https://adamsilver.io/gdcc
Design newsletter:
https://adamsilver.io/newsletter
Good Design Crash Course (free):
https://adamsilver.io/gdcc
Github’s Design System now bans toast messages.
In case you don’t know, toast messages are little messages shown on top of the UI to give feedback about an action that you’ve just taken.
Banning toast messages is an excellent decision because they have bad UX and are terrible for accessibility.
In case you don’t know, toast messages are little messages shown on top of the UI to give feedback about an action that you’ve just taken.
Banning toast messages is an excellent decision because they have bad UX and are terrible for accessibility.
November 20, 2025 at 12:15 PM
Github’s Design System now bans toast messages.
In case you don’t know, toast messages are little messages shown on top of the UI to give feedback about an action that you’ve just taken.
Banning toast messages is an excellent decision because they have bad UX and are terrible for accessibility.
In case you don’t know, toast messages are little messages shown on top of the UI to give feedback about an action that you’ve just taken.
Banning toast messages is an excellent decision because they have bad UX and are terrible for accessibility.
Last week I shared the first two laws of form design:
Law 1: Nobody wants to use your form
Law 2: Completion time = Question Time + Pause Time
Here’s the final law:
Law 3: Users will make mistakes no matter how well your form is designed.
Law 1: Nobody wants to use your form
Law 2: Completion time = Question Time + Pause Time
Here’s the final law:
Law 3: Users will make mistakes no matter how well your form is designed.
November 18, 2025 at 12:15 PM
Last week I shared the first two laws of form design:
Law 1: Nobody wants to use your form
Law 2: Completion time = Question Time + Pause Time
Here’s the final law:
Law 3: Users will make mistakes no matter how well your form is designed.
Law 1: Nobody wants to use your form
Law 2: Completion time = Question Time + Pause Time
Here’s the final law:
Law 3: Users will make mistakes no matter how well your form is designed.
New form design tip: end with one thing per page.
You may have heard of this rule:
➡︎ Start with one thing per page.
This was first written about by designers Tim Paul and Caroline Jarrett.
In case you’re not familiar...
You may have heard of this rule:
➡︎ Start with one thing per page.
This was first written about by designers Tim Paul and Caroline Jarrett.
In case you’re not familiar...
November 17, 2025 at 12:15 PM
New form design tip: end with one thing per page.
You may have heard of this rule:
➡︎ Start with one thing per page.
This was first written about by designers Tim Paul and Caroline Jarrett.
In case you’re not familiar...
You may have heard of this rule:
➡︎ Start with one thing per page.
This was first written about by designers Tim Paul and Caroline Jarrett.
In case you’re not familiar...
Yesterday, I shared the first law of form design:
➡︎ Nobody wants to use your form.
Like I said yesterday, it’s crucial to know because it emphasises respecting the user over trying to make your form fun, engaging, novel or “on brand”.
➡︎ Nobody wants to use your form.
Like I said yesterday, it’s crucial to know because it emphasises respecting the user over trying to make your form fun, engaging, novel or “on brand”.
November 13, 2025 at 12:22 PM
Yesterday, I shared the first law of form design:
➡︎ Nobody wants to use your form.
Like I said yesterday, it’s crucial to know because it emphasises respecting the user over trying to make your form fun, engaging, novel or “on brand”.
➡︎ Nobody wants to use your form.
Like I said yesterday, it’s crucial to know because it emphasises respecting the user over trying to make your form fun, engaging, novel or “on brand”.
Last week I shared my 3 laws of form design.
Here’s a breakdown of the first law which is perfectly captured by a question one of my subscribers asked me:
“How can we bring joy to people who use enterprise applications for 40 hours a week?”
Here’s a breakdown of the first law which is perfectly captured by a question one of my subscribers asked me:
“How can we bring joy to people who use enterprise applications for 40 hours a week?”
November 12, 2025 at 12:53 PM
Last week I shared my 3 laws of form design.
Here’s a breakdown of the first law which is perfectly captured by a question one of my subscribers asked me:
“How can we bring joy to people who use enterprise applications for 40 hours a week?”
Here’s a breakdown of the first law which is perfectly captured by a question one of my subscribers asked me:
“How can we bring joy to people who use enterprise applications for 40 hours a week?”
"User needs are a harmful concept."
Will Myddelton, who led product at GDS said that.
Here's why he said it (and what he suggests instead):
(1) It's confusing - even senior researchers at GDS didn't understand what it meant
Will Myddelton, who led product at GDS said that.
Here's why he said it (and what he suggests instead):
(1) It's confusing - even senior researchers at GDS didn't understand what it meant
November 11, 2025 at 12:15 PM
"User needs are a harmful concept."
Will Myddelton, who led product at GDS said that.
Here's why he said it (and what he suggests instead):
(1) It's confusing - even senior researchers at GDS didn't understand what it meant
Will Myddelton, who led product at GDS said that.
Here's why he said it (and what he suggests instead):
(1) It's confusing - even senior researchers at GDS didn't understand what it meant
I regularly see user needs written like this:
→ As a user
→ I need to be able to filter the messages by type
→ So that I can find the message I'm looking for
But that's just a solution written as a need.
Instead it should read more like:
→ As a user
→ I need to be able to filter the messages by type
→ So that I can find the message I'm looking for
But that's just a solution written as a need.
Instead it should read more like:
November 10, 2025 at 12:15 PM
I regularly see user needs written like this:
→ As a user
→ I need to be able to filter the messages by type
→ So that I can find the message I'm looking for
But that's just a solution written as a need.
Instead it should read more like:
→ As a user
→ I need to be able to filter the messages by type
→ So that I can find the message I'm looking for
But that's just a solution written as a need.
Instead it should read more like:
“But that’s a lot of clicks”
I hear this from stakeholders (and even UI/UX designers) quite regularly when I share flows with multiple steps.
But here’s the truth:
Users don’t care about clicks, as long as each click takes them logically towards their goal.
The real problem is...
I hear this from stakeholders (and even UI/UX designers) quite regularly when I share flows with multiple steps.
But here’s the truth:
Users don’t care about clicks, as long as each click takes them logically towards their goal.
The real problem is...
November 6, 2025 at 12:15 PM
“But that’s a lot of clicks”
I hear this from stakeholders (and even UI/UX designers) quite regularly when I share flows with multiple steps.
But here’s the truth:
Users don’t care about clicks, as long as each click takes them logically towards their goal.
The real problem is...
I hear this from stakeholders (and even UI/UX designers) quite regularly when I share flows with multiple steps.
But here’s the truth:
Users don’t care about clicks, as long as each click takes them logically towards their goal.
The real problem is...
Over the last 20 years I’ve collected 83 form design rules.
For example, rule 7 is:
Every input needs a label
→ Sighted users see them
→ Screen readers announce them
→ Motor-impaired users can more easily set focus to the input thanks to the larger hit area.
For example, rule 7 is:
Every input needs a label
→ Sighted users see them
→ Screen readers announce them
→ Motor-impaired users can more easily set focus to the input thanks to the larger hit area.
November 4, 2025 at 12:15 PM
Over the last 20 years I’ve collected 83 form design rules.
For example, rule 7 is:
Every input needs a label
→ Sighted users see them
→ Screen readers announce them
→ Motor-impaired users can more easily set focus to the input thanks to the larger hit area.
For example, rule 7 is:
Every input needs a label
→ Sighted users see them
→ Screen readers announce them
→ Motor-impaired users can more easily set focus to the input thanks to the larger hit area.
For the last 20+ years, I’ve built and designed various products and services that are full of forms.
And most of them had a lot of UX and accessibility issues.
But I realised that every solution I’ve ever come up with to address these issues can be traced back to 3 simple laws...
And most of them had a lot of UX and accessibility issues.
But I realised that every solution I’ve ever come up with to address these issues can be traced back to 3 simple laws...
October 30, 2025 at 12:44 PM
For the last 20+ years, I’ve built and designed various products and services that are full of forms.
And most of them had a lot of UX and accessibility issues.
But I realised that every solution I’ve ever come up with to address these issues can be traced back to 3 simple laws...
And most of them had a lot of UX and accessibility issues.
But I realised that every solution I’ve ever come up with to address these issues can be traced back to 3 simple laws...
Design tip: don't test two versions of a design (at the same time)
I often hear designers and product managers say:
“Let's test both versions and see which is better”
Sounds reasonable, except that there are a bunch of downsides with this (and it’s totally unnecessary)...
I often hear designers and product managers say:
“Let's test both versions and see which is better”
Sounds reasonable, except that there are a bunch of downsides with this (and it’s totally unnecessary)...
October 23, 2025 at 11:15 AM
Design tip: don't test two versions of a design (at the same time)
I often hear designers and product managers say:
“Let's test both versions and see which is better”
Sounds reasonable, except that there are a bunch of downsides with this (and it’s totally unnecessary)...
I often hear designers and product managers say:
“Let's test both versions and see which is better”
Sounds reasonable, except that there are a bunch of downsides with this (and it’s totally unnecessary)...
UI/UX tip: write form labels that make sense in all contexts.
For example, let’s imagine you need to ask the user to provide a reason for rejecting an application.
You could use different labels in different contexts, for example:
For example, let’s imagine you need to ask the user to provide a reason for rejecting an application.
You could use different labels in different contexts, for example:
October 17, 2025 at 11:15 AM
UI/UX tip: write form labels that make sense in all contexts.
For example, let’s imagine you need to ask the user to provide a reason for rejecting an application.
You could use different labels in different contexts, for example:
For example, let’s imagine you need to ask the user to provide a reason for rejecting an application.
You could use different labels in different contexts, for example:
Accessibility tip: visually hidden content isn’t always accessible, even in screen readers.
For example, let’s say you have a table with a column that shows acronyms.
You say to yourself “that’s not accessible, because screen reader users will hear “I. M. P. L.”
For example, let’s say you have a table with a column that shows acronyms.
You say to yourself “that’s not accessible, because screen reader users will hear “I. M. P. L.”
October 16, 2025 at 11:15 AM
Accessibility tip: visually hidden content isn’t always accessible, even in screen readers.
For example, let’s say you have a table with a column that shows acronyms.
You say to yourself “that’s not accessible, because screen reader users will hear “I. M. P. L.”
For example, let’s say you have a table with a column that shows acronyms.
You say to yourself “that’s not accessible, because screen reader users will hear “I. M. P. L.”
Just in a workshop discussing the pros and cons of using the GOV Prototype Kit over something like Figma.
Here’s the advantages:
1. Once you know the basics, you can build and iterate much quicker than in Figma - especially for complex journeys.
Here’s the advantages:
1. Once you know the basics, you can build and iterate much quicker than in Figma - especially for complex journeys.
October 10, 2025 at 11:15 AM
Just in a workshop discussing the pros and cons of using the GOV Prototype Kit over something like Figma.
Here’s the advantages:
1. Once you know the basics, you can build and iterate much quicker than in Figma - especially for complex journeys.
Here’s the advantages:
1. Once you know the basics, you can build and iterate much quicker than in Figma - especially for complex journeys.
I asked ChatGPT “How do you add hint text to radio buttons?"
It suggested:
“If you want the hint to appear when the user hovers on the radio button, use a tooltip for a cleaner design”
Let’s break this down:
→ ‘If you want’
Design is not about what you want. It’s about what users need.
It suggested:
“If you want the hint to appear when the user hovers on the radio button, use a tooltip for a cleaner design”
Let’s break this down:
→ ‘If you want’
Design is not about what you want. It’s about what users need.
October 8, 2025 at 11:15 AM
I asked ChatGPT “How do you add hint text to radio buttons?"
It suggested:
“If you want the hint to appear when the user hovers on the radio button, use a tooltip for a cleaner design”
Let’s break this down:
→ ‘If you want’
Design is not about what you want. It’s about what users need.
It suggested:
“If you want the hint to appear when the user hovers on the radio button, use a tooltip for a cleaner design”
Let’s break this down:
→ ‘If you want’
Design is not about what you want. It’s about what users need.
Enterprise products are often prone to spinnageddon.
This is where each component “loads itself” async with a spinner.
This is a slow, inaccessible experience that's totally unnecessary.
Instead, render on the server.
You’ll get the standard, accessible, browser loading indicator for free.
This is where each component “loads itself” async with a spinner.
This is a slow, inaccessible experience that's totally unnecessary.
Instead, render on the server.
You’ll get the standard, accessible, browser loading indicator for free.
October 7, 2025 at 11:15 AM
Enterprise products are often prone to spinnageddon.
This is where each component “loads itself” async with a spinner.
This is a slow, inaccessible experience that's totally unnecessary.
Instead, render on the server.
You’ll get the standard, accessible, browser loading indicator for free.
This is where each component “loads itself” async with a spinner.
This is a slow, inaccessible experience that's totally unnecessary.
Instead, render on the server.
You’ll get the standard, accessible, browser loading indicator for free.
Over 1,500 UI/UX designers have watched the Good Design Crash Course.
In the course, I explain what design actually is (hint: it’s not just about aesthetics).
And I reveal the 4 principles I use every day as a designer to make sure that what I design is actually good.
That is:
In the course, I explain what design actually is (hint: it’s not just about aesthetics).
And I reveal the 4 principles I use every day as a designer to make sure that what I design is actually good.
That is:
September 30, 2025 at 11:15 AM
Over 1,500 UI/UX designers have watched the Good Design Crash Course.
In the course, I explain what design actually is (hint: it’s not just about aesthetics).
And I reveal the 4 principles I use every day as a designer to make sure that what I design is actually good.
That is:
In the course, I explain what design actually is (hint: it’s not just about aesthetics).
And I reveal the 4 principles I use every day as a designer to make sure that what I design is actually good.
That is:
UI/UX designers and frontend devs — what’s your go-to input mask library?
September 24, 2025 at 8:05 AM
UI/UX designers and frontend devs — what’s your go-to input mask library?
Last week, designer Anthony Hobday noticed WhatsApp’s button is misaligned.
You can see in the screenshot that there’s more margin above the button than below it - something most designers would say is sloppy.
And perhaps it is.
You can see in the screenshot that there’s more margin above the button than below it - something most designers would say is sloppy.
And perhaps it is.
September 23, 2025 at 11:15 AM
Last week, designer Anthony Hobday noticed WhatsApp’s button is misaligned.
You can see in the screenshot that there’s more margin above the button than below it - something most designers would say is sloppy.
And perhaps it is.
You can see in the screenshot that there’s more margin above the button than below it - something most designers would say is sloppy.
And perhaps it is.
Last Tuesday, my article about using “Your” and “My” in user interfaces went viral on Hacker News.
Hacker News (if you don’t know) is a site where people discuss and upvote ideas in tech/design.
The gist of my article was:
✅ Use “Your” when communicating to the user
And:
Hacker News (if you don’t know) is a site where people discuss and upvote ideas in tech/design.
The gist of my article was:
✅ Use “Your” when communicating to the user
And:
September 22, 2025 at 11:15 AM
Last Tuesday, my article about using “Your” and “My” in user interfaces went viral on Hacker News.
Hacker News (if you don’t know) is a site where people discuss and upvote ideas in tech/design.
The gist of my article was:
✅ Use “Your” when communicating to the user
And:
Hacker News (if you don’t know) is a site where people discuss and upvote ideas in tech/design.
The gist of my article was:
✅ Use “Your” when communicating to the user
And:
My article about “Your” vs “My” in user interfaces is trending on Hacker News.
Should I brave the comments?
Should I brave the comments?
September 16, 2025 at 9:09 AM
My article about “Your” vs “My” in user interfaces is trending on Hacker News.
Should I brave the comments?
Should I brave the comments?
A couple of days ago I wrote about how the best modal is a page.
Lots of designers agreed (surprisingly).
But some got a bit upset by it. Thought I was rage baiting or something.
The truth is that modals are much harder to use than a dedicated page.
Lots of designers agreed (surprisingly).
But some got a bit upset by it. Thought I was rage baiting or something.
The truth is that modals are much harder to use than a dedicated page.
September 3, 2025 at 11:15 AM
A couple of days ago I wrote about how the best modal is a page.
Lots of designers agreed (surprisingly).
But some got a bit upset by it. Thought I was rage baiting or something.
The truth is that modals are much harder to use than a dedicated page.
Lots of designers agreed (surprisingly).
But some got a bit upset by it. Thought I was rage baiting or something.
The truth is that modals are much harder to use than a dedicated page.
UX tip: the best modal dialog is a page
1. Click link
2. Go to page
3. Confirm thing
So why use a modal?
I can only think of bad reasons like:
➡︎ 1. It’s quicker than a page refresh
I’ve used pages for years, not seen one issue in research related to speed.
1. Click link
2. Go to page
3. Confirm thing
So why use a modal?
I can only think of bad reasons like:
➡︎ 1. It’s quicker than a page refresh
I’ve used pages for years, not seen one issue in research related to speed.
September 1, 2025 at 11:15 AM
UX tip: the best modal dialog is a page
1. Click link
2. Go to page
3. Confirm thing
So why use a modal?
I can only think of bad reasons like:
➡︎ 1. It’s quicker than a page refresh
I’ve used pages for years, not seen one issue in research related to speed.
1. Click link
2. Go to page
3. Confirm thing
So why use a modal?
I can only think of bad reasons like:
➡︎ 1. It’s quicker than a page refresh
I’ve used pages for years, not seen one issue in research related to speed.
UX observation: I often see UI referring to the user’s stuff using “My”.
For example, ‘My account’.
This seems fine for a navigation menu, but it doesn’t make sense in other contexts, like in an email notification...
For example, ‘My account’.
This seems fine for a navigation menu, but it doesn’t make sense in other contexts, like in an email notification...
August 29, 2025 at 11:15 AM
UX observation: I often see UI referring to the user’s stuff using “My”.
For example, ‘My account’.
This seems fine for a navigation menu, but it doesn’t make sense in other contexts, like in an email notification...
For example, ‘My account’.
This seems fine for a navigation menu, but it doesn’t make sense in other contexts, like in an email notification...
Yesterday, I shared my third law of form design:
Users will make mistakes no matter how well your form is designed.
It’s not that you shouldn’t do everything in your power to reduce errors...
Users will make mistakes no matter how well your form is designed.
It’s not that you shouldn’t do everything in your power to reduce errors...
July 31, 2025 at 8:19 AM
Yesterday, I shared my third law of form design:
Users will make mistakes no matter how well your form is designed.
It’s not that you shouldn’t do everything in your power to reduce errors...
Users will make mistakes no matter how well your form is designed.
It’s not that you shouldn’t do everything in your power to reduce errors...