Don't Make Me Click

This is another interesting link, a talk by the author of the linked post, with a similar focus (Don't make me click): ▶ this video

in “Calculate The Efficiency of Your User Interface” · View on HN

Read Don't Make Me Think! by Steve Krug. Also watch this talk titled "Don't Make Me Click!": ▶ this video It's really helpful to deconstruct website designs. So I frequently look at a website and think about sections I would redesign, how I would do it, and most importantly - why. Sometimes I break out an image editing program and redesign the sections or even the entire page. The huge advantage with this approach is that the content is already provided. When I started learning web design, I would come up with hypothetical website ideas (like "I'll design a website for a law firm") and then try to create the content in addition to the website. But it doesn't work like that. You need content to work with before you can create the site. So you're much better off finding an actual law firm website, using their content, and redesigning sections or the entire page. Along the way, with a little help from usability resources like those mentioned above, you will also figure out which content actually belongs, which doesn't, and why. But the point is this: take something that's already built, break it down, and rebuild it.

in “Ask YC: Where to learn web design?” · View on HN

I've actually been thinking about this type of interface for years and have never really got the opportunity to implement my ideas. Are you familiar with the Raskins' work? [link] [link] ▶ this video

in “Spectre.Console lets you make beautiful console apps with .NET Core” · View on HN

Some of the same points Aza Askin did a few years ago on his Don't make me click presentation[1] : "The best interface for a shovel is a hole where you need it" [1] ▶ this video

in “The Cooper Journal: The best interface is no interface” · View on HN