Adam Silver
“Your” vs “My” in user interfaces
The problem with good design
A confession
TireRack’s clever, conversion-boosting UX
“I’m not a designer but...”
Do you trust design advice from ChatGPT?
Are there exceptions to the ‘avoid multi-column forms’ rule?
My clever solution for handling multiple submit buttons
Why the ‘none of the above’ checkbox pattern worries me
My definition of form design
How to usability test your product (if you want bad UX)
Royal Mail is literally the opposite of user-centered
Should destructive buttons be hard to find?
Losing is part of being a designer (but that doesn’t have to be you)
Why toggle switches suck (and what to do instead)
I took David Hamill’s UX challenge (how did I do?)
Don’t use the maxlength attribute to stop users from exceeding the limit
Figma prototypes vs HTML prototypes
Don’t use paracetamol to fix bad UX
Why Anthony Hobday’s sentence-style form is bad UX (and what to do instead)
Sliders degrade UX (so do this instead)
3 common examples of button text that degrades UX and how to rewrite them so they’re clear
7 reasons to replace advanced search with filters so users can easily find what they need
3 questions to evaluate design patterns and avoid unnecessary work that degrades UX
The problem with disabling paste and what to do instead
5 key design system elements to build trust and maximise uptake
4 design principles I use every day to avoid bad UX and create products that work for everyone
The problem with input masks and what to do instead
The problem with sticky menus that appear on scroll and what to do instead
4 common mistakes UI/UX designers make when trying to help users spot required form fields (and what user research shows is better)
The problem with automatically focusing the first input and what to do instead
The problem with nested fieldsets and how to avoid them
The billion dollar unsubscribe link
The problem with disabled buttons and what to do instead
The problem with sticky menus and what to do instead
Page title conventions
Designing a time input
Material Design text fields are badly designed
Stopping Chrome from ignoring autocomplete=off
A few notes about A/B testing from Jared Spool
Avoiding tab styles for navigation
Interaction designers: how well do you work with developers and content designers?
Bidirectional scrolling: what’s not to like?
Pressing back after deleting something
The trouble with mailto email links and what to do instead
A quick crit of HEY email
Form design: multiple inputs versus one input
Routing conventions
Rules for cookie banners
Tips for running a good remote meeting
3 little rules for good team communication
The problem with toast messages and what to do instead
Building an accessible autocomplete control
Form design patterns webinar, course update, January resolutions
Building trust as a designer
JavaScript isn’t always available and it’s not the user’s fault
Where to put buttons on forms
Launching a service, contribution the bank details pattern, design system community building
The problem with tooltips and what to do instead
Form design: from zero to hero all in one blog post
Defining graceful degradation, Patterns Day, journey mapping, question protocol mapping
In defence of graceful degradation and where progressive enhancement comes in
The problem with web components
Caseworking meetup notes, design system uptake, writing is hard, soft skills are hard
Semantic HTML and ARIA explained
Getting agreement on big decisions, versioning prototype routes, pair writing
Prototyping versioning, ConCon8, beyond screens
Prototype versioning, namespacing design systems, discussing a header component
Prototype kit extensions, small checkboxes and radio buttons, multi-select autocomplete
Semantic HTML, design crits, GOV.UK form components in Angular, pattern sharing
React is not a library, Angular generates wrappers, semantic HTML, defining UX
Writing workflow, context switching and some useful links
Angular forms, hiding elements, boring development, responsive design mindsets
Extending the GOV.UK Design System, progressive enhancement, naming patterns
User interfaces: hiding content should be a last resort
Form builders, design system thoughts, new design system components
Handling links in Angular, buttons versus links, design system architecture, journey mapping
Defining interaction design, scoping a rich text editor component, links inside SPAs, fudgability
How to avoid optional form fields with a conditional reveal
Form design: when to use the number input
Thinking differently about progressive enhancement
Content is the user experience and what the deuce is content design?
Buttons shouldn't have a hand cursor part 2
Progressive enhancement explained simply
But sometimes buttons look like links
4 steps to design fast experiences
The problem with live validation and what to do instead
The problem with float labels and what to do instead
The problem with atomic CSS
Stop using device breakpoints
Universal design checklist
Don’t initialise Javascript automagically
Semantic class names: are you being too generic or too specific?
Browsers are different but so what?
Making view templates as dumb as possible
Buttons shouldn't have a hand cursor
Always use a label
The problem with placeholders and what to do instead
How we cut our MVP in half to launch KIDLY
Everything I know about speaking at conferences
Embracing simplicity
Design is not just how it looks
Hover menus are problematic
Why we stopped breaking down stories into tasks
7 reasons why infinite scrolling is a bad idea
The hidden cost of one bad design
Designing honestly for the web
Designing a responsive menu without a hamburger
Progressively enhanced Javascript
Addendum to the boring front-end developer
The disadvantages of Javascript polyfills
The disadvantages of CSS preprocessors
The role of the Front-end Developer
Technical wanking
Don't use AJAX for personalised content
The boring front-end developer
Select boxes shouldn’t submit on change
JavaScript inheritance
The problem with single page applications
Javascript namespacing
Forms with multiple submit buttons are problematic