3 ms·

So basically he is saying that some parts that have been traditionally considered a part of UI design are not a part of UI design but of UX and that is why UX a

by Sarien 13y ago

So basically he is saying that some parts that have been traditionally considered a part of UI design are not a part of UI design but of UX and that is why UX and UI are different. "Boohoo, nobody takes me seriously, they all think I just make pretty dialogs." I know that feeling but I don't think coming up with more names and vague definitions that nobody knows is going to help.

maaaats 13y ago
Taking an entire article and expressing it as "boohoo" is not a good way to have a meaningful discussion.
- TheZenPsycho 13y ago
  neither is writing an entire article that has a lot of words, and yet says nothing.
seivan 13y ago
Performance and Speed is UX. Something UI designers never really will understand. It's not just UX, but the only UX that's actually quite objective. No one ever goes "Oh gosh this app is too fast" Another non developer talking about things that they can't implement.
- TheZenPsycho 13y ago
  Condescension is not a very good technique for persuasion.
- eflowers 13y ago
  I agree. That's one of those places where being in a UX role is way outside of UI design, and I'm taking the apps on-site with customers (I am mostly b2b) and observing and testing them as they use it. Recording their responses, as well as the applications. When logging in to the system takes 40 seconds because of database performance (or lack of), that's a UX insight that needs to be observed and reported. That's not something I can control but it has a huge impact on the user's experience. There's an element of user-advocacy that I'm doing where I take the experience they are having and translate it back into business, design, and development goals as when someone is trying to use an enterprise piece of software and the experience is terrible, that is going to fall on designers, developers, PM's, and all the other people involved in the creation of the "thing" which becomes the user's experience. That's another ambiguous situation. I go spend 2 days with users out at a company HQ, and I come back with tons of data that now has to be consumed by devs, designers, pm, marketers, executives, QA, customer service etc etc. The experience of what we build is a collection of every role in the entire company as far as the user is concerned, and all those various business roles need that UX information brought back. So at this point I'm so far from UI and visual design I'm closer to a PM or product owner now, but soon will be jumping back into the design an development realm to start to fix those experience problems.. unless the problems result in bad business drivers or invalid use-cases, so then I'm back at the PM and management table, I still can't find a clear distinction about what I'm supposed to say I do. I just know that there is a certain disservice to just tell people "UI design, look and feel."

by Sarien 13y ago

maaaats 13y ago

Taking an entire article and expressing it as "boohoo" is not a good way to have a meaningful discussion.

TheZenPsycho 13y ago
neither is writing an entire article that has a lot of words, and yet says nothing.

seivan 13y ago

Performance and Speed is UX. Something UI designers never really will understand. It's not just UX, but the only UX that's actually quite objective. No one ever goes "Oh gosh this app is too fast" Another non developer talking about things that they can't implement.

TheZenPsycho 13y ago
Condescension is not a very good technique for persuasion.
eflowers 13y ago
I agree. That's one of those places where being in a UX role is way outside of UI design, and I'm taking the apps on-site with customers (I am mostly b2b) and observing and testing them as they use it. Recording their responses, as well as the applications. When logging in to the system takes 40 seconds because of database performance (or lack of), that's a UX insight that needs to be observed and reported. That's not something I can control but it has a huge impact on the user's experience. There's an element of user-advocacy that I'm doing where I take the experience they are having and translate it back into business, design, and development goals as when someone is trying to use an enterprise piece of software and the experience is terrible, that is going to fall on designers, developers, PM's, and all the other people involved in the creation of the "thing" which becomes the user's experience. That's another ambiguous situation. I go spend 2 days with users out at a company HQ, and I come back with tons of data that now has to be consumed by devs, designers, pm, marketers, executives, QA, customer service etc etc. The experience of what we build is a collection of every role in the entire company as far as the user is concerned, and all those various business roles need that UX information brought back. So at this point I'm so far from UI and visual design I'm closer to a PM or product owner now, but soon will be jumping back into the design an development realm to start to fix those experience problems.. unless the problems result in bad business drivers or invalid use-cases, so then I'm back at the PM and management table, I still can't find a clear distinction about what I'm supposed to say I do. I just know that there is a certain disservice to just tell people "UI design, look and feel."