Awesome list. One point I’d add that changed how I think about UI and UX is being aware when UI reflects internal code structure instead of just doing what a user would want to see.
The latter is harder, so engineers tend to avoid it, often subconsciously.
> UI reflects internal code structure instead of just doing what a user would want to see.
Some of that depends on the audience for the app. For a technically sophisticated user base, having an interface that comes closer to the level of the underlying implementation can be quite powerful (and give a system a feeling of gestalt or wholeness that's quite satisfying).
That's one of the aspects of Emacs that I find the most valuable. A command is just a function in the underlying Lisp, etc.
But for less technical users, or even technical users in a 'off hours' or less technicial setting, this sort of UI can require an unduly high investment.
mschaef|7 years ago
Some of that depends on the audience for the app. For a technically sophisticated user base, having an interface that comes closer to the level of the underlying implementation can be quite powerful (and give a system a feeling of gestalt or wholeness that's quite satisfying).
That's one of the aspects of Emacs that I find the most valuable. A command is just a function in the underlying Lisp, etc.
But for less technical users, or even technical users in a 'off hours' or less technicial setting, this sort of UI can require an unduly high investment.