Are they all necessary? Could they be simplified or deferred? It is important that the questions are worded in such a way that people will understand why you're asking them. Three big takeaways for me were:ġ) Think more about the structure of the form and the questions being answered. Each design solution is explained in detail and backed up with results from real-life usability tests, which could come in handy during discussions with clients. It addresses many different aspects of form design, from big picture ideas like "do I even need a form here?" to small details like the placement and graphic used for an Info button. The book is organized into three sections structure, elements and interaction. Luke's writing style is conversational and approachable, making Web Form Design an easy read. There are plenty of screenshots and diagrams that help illustrate his points. It is a book full of examples (good and bad) and actionable solutions for common web form problems. Once I finally opened the book, I made an awesome discovery: this is not a book full of code. The author sums it up by saying "Forms suck. But this book points out how much we can be doing to improve this crucial point of interaction.
And some of them are really awful, right? As designers, its tempting to copy a form directly from a client's document, add a few quick styles to pretty it up and let the developers worry about how they actually work. From simple logins to multi-step purchasing forms, chances are you fill out a few dozen every day. Forms are a none-to-fun necessity for nearly any website you touch. So why read a book about forms? Think about it. He knows what he's talking about, and he knows how to talk about it without making your eyes glaze over. He is a regular at web conferences and shows up in the occasional podcast as well. He writes a blog on usability and interface design found at. He's the Senior Principal of Product Ideation & Design at Yahoo! and was also a Lead User Interface Designer for eBay. If you haven't heard of Luke Wroblewski before its time to get acquainted. I've slogged through plenty of web dev books that bored me to tears, dutifully taking notes and highlighting long chunks of code.
I was eager to dive in and start learning, but I wasn't too excited to crack open a 200+ page book about web forms. One of my goals for the new year is to improve my understanding of user experience design. Until reading this book, I didn't know how much I didn't know about form design.
0 kommentar(er)
