3 ms·
Pieces like this might give an illusion that by following the listed rules you’ll achieve “intuitive UX” (sic). I believe they could be useful if you already ha
by goblin89 7y ago
Pieces like this might give an illusion that by following the listed rules you’ll achieve “intuitive UX” (sic). I believe they could be useful if you already have the first principles somewhat internalized, but otherwise are likely to be a dangerous distraction.
First principles include knowing that you communicate with the user through interface, being intentional, having an overall vision, being consistent[0].
People’s expectations as to exact UI layout and behavior can vary a lot, depending on their background and previous experience (for example, on macOS I personally often look for things & shortcuts in menu bar first instead of scouting app’s interface). However, people are not stupid, they learn.
[0] Including consistency in evolution across product lifetime.
- roguesherlock 7y agoI'm intrigued. How does one internalise this (first principles)?
- goblin89 7y agoTo internalize something is to make it come naturally without reminding yourself about it every time. Practice, reading material on those topics (books like “The Design of Everyday Things”, “Notes on Graphic Design and Visual Communication”) help.
- roguesherlock 7y agomakes sense. thanks!
- vmurthy 7y agoAs a total newbie to UX (I used to be a middleware/back-end developer :-P), I read this article differently. The article mentioned a list of things NOT to do which has its own uses. Let me give you some context: I currently work as a PM at a startup. We don't really have a UI/UX guy since the last full-stack dev quit. By avoiding a lot of these issues in the first place, I , as the PM can ensure that my customers don't get pissed off because my team mates have built a solid product (code quality, functionality, stability etc) but with glaring UX howlers :-). Via negativa FTW!