Not a reason to make no effort into having as proper error messages as possible. Still there's some truth there that trying to have a really useful error message is a fool's errand.

This is an important request. It has safety implications. It is non-binding request of course, but the insurance companies pay attention to it and so could have an impact.

Or why wording matters... this is clearly a user design fail in this case.

This introduced lack on consistency and predictability in how you can interact with a GUI component is a problem, this will also reduce accessibility. There was value in this "tradition" of the square checkbox vs round radio button.

There was definitely something we lost from the early days of the web. It was not perfect, far from it, but some of that spark is missing.

It's nice that we get more content usable on mobiles... but this shouldn't come at the expense of bad usability when on desktops.

Some things we tend to not notice... the scroll bars need a way to be brought back and to be large for better accessibility.

OK, this is a very bleak view... maybe a bit over the top I'm unsure. There seems to be some truth to it though.

Good set of patterns indeed. The article is web oriented but this makes sense in other type of applications as well.

Black has been getting too much of a bad reputation in the last few years. This article makes a good job arguing for a more balanced view.

Interesting idea, personas help with producing features, something is needed to prevent features we don't wante.

Interesting ideas for using large language models. There is a world beyond the chatbot interface and it might bring more value to users and avoid some of the pitfalls of anthropomorphisation.

Probably the best analysis of the new Apple device I've seen so far. Focuses more on the design of the user experience and compares with the strategy behind other similar devices. There are likely a lesson or two to be drawn from it.

Clearly the UI design matters quite a bit in term of how addictive all those social network systems are. The alternative proposed here is interesting, I wish it'd be more widely implemented.

Plenty of good advises for dealing with text in interfaces. It's a bit too much focused on phone and watch for my taste glancing over challenges specific to larger form factors. Still this can be useful to keep in mind.

Very nice set of rules. They are very simple to apply individually. The art is in respecting it all of course.

Indeed, quite a lot of spinners and progress bars are not tied to anything meaningful. This definitely creates uncertainty from the user perspective.

Excellent response to an article full of misconceptions about the Agile approaches. This turns in a good summary of cargo cult agile we see in the wild and the original intent. I especially like how it points out approaches to properly integrate UX as well.

Not very scientific, but indeed thought provoking and taps into safety considerations.

A bit old but interesting finding. Kind of confirms my own view about it: it's best when everyone (not just designers) can interact with the users of the system you're building.