In the early 1990s, cognitive scientist Don Norman took a job at Apple with the title "User Experience Architect" — one of the first uses of the phrase in an industry setting. He later said he coined "user experience" deliberately because he found "usability" too narrow: he wanted a term covering everything about a person's interaction with a product, including industrial design, the manual, the packaging, even the support call. Three decades later, "user experience" and "user interface" are used constantly, often interchangeably, despite having genuinely separate intellectual histories.
"User interface" is the older term, rooted in human-computer interaction (HCI) research going back to the 1970s and 80s, when the challenge was literally getting a person and a computer to exchange information at all — command lines, then graphical interfaces pioneered at Xerox PARC and popularized by the Macintosh. It described a fairly literal thing: the screen, the inputs, the point of contact between human and machine.
"User experience" arrived later and from a different direction — industrial design and cognitive psychology, concerned with the full arc of a person's interaction with a product or service, not just the screen. Norman's framing pulled in factors that had nothing to do with a graphical interface at all: how a product is unboxed, how confusing its error states feel, whether a return process leaves someone frustrated.
Both fields have intellectual roots that predate the terms themselves by decades. Vannevar Bush's 1945 essay "As We May Think" imagined the Memex, a hypothetical desk-sized device for storing and cross-referencing information, and is often cited as an early conceptual ancestor of hypertext and information architecture — the structural thinking that would later become central to UX. Douglas Engelbart's 1968 "Mother of All Demos" introduced the computer mouse and windowed, collaborative computing, work that laid the physical and conceptual groundwork for what a "user interface" would even mean once graphical computing arrived. Xerox PARC's research through the 1970s turned those ideas into the first real graphical user interfaces — icons, windows, and pointers — which Apple and later Microsoft popularized commercially in the 1980s.
Notably, Apple engineer Jef Raskin — who started the Macintosh project — was an early and vocal advocate for the term "user interface" itself, and later wrote an influential book, "The Humane Interface" (2000), arguing that interface design should be treated as a rigorous discipline with measurable principles, not a matter of taste. Around the same period, Jakob Nielsen was publishing foundational usability research, including his widely cited 1994 heuristics for interface evaluation, which helped formalize "usability" as a testable property rather than a vague impression — work that predates and directly informs how UX is practiced today.
The international standard ISO 9241-210 defines user experience roughly as a person's perceptions and responses resulting from the use of a product, system, or service — deliberately broader than "did the buttons work." Most professional definitions of UI, by contrast, stay closer to the original HCI meaning: the specific visual and interactive layer through which a user operates a system. UX is the superset; UI is one channel through which UX gets delivered, alongside things like customer support, onboarding emails, and even shipping speed.
The vocabulary around UX and UI has kept expanding as the field matured, and a few adjacent terms are worth being able to place:
None of these terms have perfectly agreed-upon boundaries across the industry — different companies and consultancies draw the lines slightly differently — but recognizing the general territory each one covers helps when reading job postings or industry writing that assumes familiarity with the distinctions.
Through the 1990s and 2000s, UI design and UX research developed somewhat separately — UI lived closer to graphic design and front-end engineering, while UX lived closer to academic HCI and usability testing labs. The rise of the "product design" title in the 2010s, particularly at software companies building fast-iterating web and mobile apps, pulled the two back together in day-to-day practice, since a single person was often expected to both structure a flow and visually execute it. The academic and vocabulary distinction never disappeared, but the day-to-day job increasingly blends both.
Despite the blending in practice, the words still carry different weight in hiring. A "UX Researcher" role signals a focus on evidence-gathering with little to no visual output expected. A "UI Designer" or "Visual Designer" role signals the opposite — strong visual craft, less emphasis on running studies. A "Product Designer" role signals the hybrid. Knowing the etymology helps decode what a company is actually asking for, since job titles in this space are inconsistently applied and the words themselves carry more information than the title alone.
One way to hold onto the distinction: UX is the older, deliberately broad idea — everything about how a product feels to use, going back to Norman's original framing that included the manual and the box. UI is the newer-in-name but older-in-practice piece — specifically the screen, the interaction layer, the part that took shape decades earlier in HCI labs before "user experience" existed as a phrase at all. When in doubt, ask whether you're talking about the whole journey or the specific screen — that question sorts UX from UI faster than any formal definition.
He's widely credited with popularizing and formalizing the term through his role and title at Apple in the early 1990s, and has spoken about coining it deliberately to be broader than "usability" or "human interface." Related ideas existed earlier in industrial design and HCI research, but Norman's framing is the one that stuck in the industry.
They're closely related but not identical. HCI is the broader academic discipline studying how people interact with computers, including UI design as one applied outcome. UI design is more specifically the practice of designing the actual visual and interactive layer, informed by HCI research but focused on shipping real products.
Mostly because smaller companies need one person to cover both, so the hiring need is genuinely combined even though the underlying skills have separate roots. It's a practical hiring shorthand rather than a claim that the two are the same discipline.