Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@NoMad Yes. Listening to bullshit things like this is how we ended up with millions of "one page" websites all looking the same. I hate that "design" so much.
It's awful to navigate, to find what you want, etc. -
@NoMad "Unfamiliar" I'd take, at least it means something. Same with "unresponsive", "x functionality isn't very discoverable", "y functionality isnt very accessible", etc.
But yeah, "intuitive" means nothing at all, and when people *do* use it, it turns out they often just mean "but it doesn't look like my facebook and I don't know what to do"... -
Well this is where your say: "What do you mean by more intuitive?"
Or: "We have a complex problem. I cannot make the problem go away as this is what we want to solve. This solution solves it. I need to understand the pain-points of our users to get a feeling on where to improve things or if teaching our user-base would suffice here." -
@CodeMasterAlex Of course you should define personas. Of course you should do lo-fi testing / prototyping, of course you should revisit and replan your interface based on feedback from that.
That still doesn't take away from the fact "intuitive" is a useless word in this context. It doesn't even add any meaning to your comment there, beyond the UI being "good". -
@k0pernikus @Midnigh-shcode The fact you have to follow it up with no clue what they mean beyond "I'm not happy with this somehow" is a pretty big clue that the information is useless.
Should clarify that this is in a professional tech environment where the people making these comments should know better. If you were asking for random comments from the general public, I'd agree (I'd also expect it.) -
@AlmondSauce "professional tech environment"
doesn't mean much, not many people in trch environments actually know enough about psychology and ux.
including those who design interfaces. (notice i didn't call them ui designers, since from my experience, in 98% of cases, they are not.) -
@AlmondSauce p. s. information that "it's wrong even though i don't know how or why" is still better than no information at all.
-
@StefanH You listed 10 examples. Each of those statements is a completely fine criticism and helpful. Hiding behind "unintuitive" as a shortcut and to expect a developer to know what you mean is unfair. Calling people lazy or stupid for not having your experience level is very unproductive.
You can use that phrase as a starting point. "Your UI is unintuitive because <reasons>." Just the word by itself is meaningless.
Am I the only person who hates people using "intuitive" when giving feedback about interface design? It's *completely* meaningless. Heck, this isn't even my design that's being critiqued and the comments make my skin crawl.
"It works well, but it's not very intuitive"
"Can we make this section of the interface more intuitive somehow?"
"I don't think our customers are finding it very intuitive, they're having lots of issues"
If I had my way everyone using the word would be kicked out of the meeting and made to wear an "I'm a moron" t-shirt for the rest of the week, especially the smug arses that act as though they've just said something profound.
rant