Thanks, Seb, appreciate it.

Makes sense to me.

That's a great idea. Might do a follow up post with some common examples.

I think we agree. If you declutter as much as possible and what you're left with means you need to hide something to help users, great.

For example, on the service I'm currently designing we have accordions and toggle menus. We tried our best not to need these things. But after the effort to declutter, and use pages as much as possible, it still makes sense to have these things in certain places. But with that said, the majority of our UI just shows the content and it works well.

What I'm more saying, is not to start with the assumption that hiding stuff is better.

Thanks for sharing this Mark.

I’ve been obsessed with form design from day one, which for me, was almost two decades ago!

And about two years ago I realised I was wasting a lot of time solving the same problems again and again. You get it—most web thingies let users register, login, search, filter, checkout and upload files etc.

While I had a growing collection of mock-ups, prototypes and code snippets I could refer back to, I didn’t have the guidance, rationale and mindset written down to go along with it.

I wanted something less fragmented. To get this stuff out of my head and onto paper. I wanted to focus on newer, bigger problems. And I wanted the web to get better at this stuff so we can all level up together.

So I decided to write a book with ten big problems to solve. Together, they cover the overwhelming majority of form design patterns we find (often done badly) across the web.

And you can't do anything these days without at least mentioning design systems so I decided to make one to accompany the book. It houses all the demos, components and patterns in the book. You'll get a link to each one at the bottom of every chapter.

And today I’m so happy to tell you the book is available to buy on Smashing Magazine—either as a beautiful hardback or ebook.

Yep, otherwise known as Jakob's law and it's a fair point against my article.

Yes, definitely have another visual cue—don't forget the hover state.

The point about One Thing Per Page was it shortens forms, meaning users get feedback after filling out each field.

Yes, they wish to move on, but they may have made a mistake. We know that they want to move on when they submit (as opposed to type/blur).

In which case, makes sense to show them their mistake then, without interrupting them.

I was joking.