News for hackers. Stuff that matters.
Re:I wrote the book on user-friendly design. What I see toda... by seanwilson on Monday October 16, 2023 @04:24PM (#37906008)
Feels like there needs to be more intuitive terminology and for it to only be used when it's helpful to the discussion.

Most of the time I see the word "affordance" used, it's dropped into the conversation where the poster should know the other commenters aren't going to know what it means, or it devolves into a discussion about the definition. I've don't hear it used outside UX circles.

During projects it's usually enough to say something like "I think we should add X so it's more obvious you can Y". I'm don't see much gain in breaking it down more or using terminology most won't remember.

Re:I wrote the book on user-friendly design. What I see toda... by _a_a_a_ on Monday October 16, 2023 @05:17PM (#37906780)
A while back someone, replying to one of my comments, mentioned affordances in C#. He simply meant procedure or function, but chose to use a fancier sanding, more abstract word which really confused me. There is too much misuse of pompous language happening where simpler, plainer descriptions work better (yes, language is also a user interface of sorts).
Re:I wrote the book on user-friendly design. What I see toda... by smcin on Tuesday October 17, 2023 @05:46PM (#37922046)
Right. "visual hint" is self-explanatory and cannot be misinterpreted, and seems to be a more common term. As a non-UX person I've never heard the UX jargon "affordance", but I've heard "visual hint" tons.