For the past several years, whenever the “UX vs UI” debate has come up amongst my designer friends, I’ve held the position that UX is not UI. UI design is one of many skills involved in strong user experience design: a good UX designer needs to be familiar with information architecture, graphic design, requirement writing, copywriting, speaking to programmers, etc, etc. A person who only excels in UI design is a mere pixel pusher.
I still agree with this. But in working through Matt Smith’s shift nudge course on UI design, I realized something. This distinction works if I’m describing things from the perspective of my industry, which is focused on UX designers. In other words, this is a debate about roles, skills, and tasks.
But Matt Smith looks at this debate by talking about digital experiences themselves, rather than describing UX designers’ roles and skills; he’s describing the product, and not the architect. And a person experiences a digital product through the user interface. If a digital experience is about taking a user from where they are (point A) to where they’d like to be (point B), this is principally accomplished through the interface itself.
To put it another way: when describing the industry, a UX designer is much more than a UI designer. But when describing an actual experience, the interface design is the core that dictates the quality of that experience.
This explains, perhaps, why UX is often seen as interface design. Digital products are experienced by way of an interface! Although many other skills are needed to fashion the right experience, in the end, it is the interface that makes the experience.
This applies mainly to a single digital product or interface. The longue duruee of UX–the plurality of experiences with a brand across a variety of products, touchpoints, and interactions–is usefully described as CX, though even there, digital interfaces of some kind can make up a majority of the interactions.