UI and UX Are Not Independent. They Never Were.

I came across a take recently that's been circulating in design circles. The argument goes something like this:

There's something in there I can work with. UI and UX are genuinely distinct disciplines. UX spans the entire journey, information architecture, task flows, error handling, performance, onboarding, and UI is the visual and interactive layer on top. So in theory, yes, a product can nail the flow and logic while looking rough around the edges.

The Selar example? Fair. A platform can solve a real problem effectively even if the visual polish isn't top-tier. That part I don't disagree with.

But calling them "independent", that's where it falls apart.

UI is not decoration sitting on top of UX. It's one of the primary delivery mechanisms of the experience itself. Visual hierarchy guides attention. Spacing affects comprehension. Colour and contrast affect accessibility. Interaction patterns, button placement, feedback states, affordances, directly shape how intuitive a flow feels.

A confusing visual layout can make a well-architected flow feel broken. So while they're distinct in concept, they're deeply interdependent in practice.

And the idea that you can evaluate them independently? Not when it comes to how users actually experience a product. The UI isn't just presenting the experience, it's actively shaping the user's perception of it.

The Checkout Test

Consider a checkout flow that's logically perfect. Three steps. Minimal inputs. Clear progression. On paper, the UX is sound.

But if the button hierarchy is confusing, if the tap targets are too small, if the visual feedback on errors is unclear, the user walks away saying "that was a bad experience."

They don't say "the UX was great but the UI let it down." They just felt friction. That distinction exists in our heads as designers. It does not exist in the user's.

The Goalposts Shift

The "bad UI, good UX" framing quietly moves the goalposts. When someone says Selar has bad UI but good UX, what they often mean is: "the core functionality works and solves my problem despite the interface."

That's not UX in its full sense. That's utility. Product-market fit. True UX quality includes how effortless, clear, and pleasant the interaction feels, and UI contributes heavily to all of that.

Voice and Lyrics

The relationship is more like voice and lyrics in a song. You can study them separately, and people specialise in one or the other. But the listener hears one thing. The delivery is part of the message.

If UI is the major mechanism through which UX reaches the user, which it is for most digital products, then evaluating the experience without accounting for the interface is like judging a speech by reading the transcript without hearing the delivery.

You're missing a fundamental layer of how it actually lands.

They're not the same thing. But calling them independent undersells how much one shapes the other. And more importantly, your users will never experience them as separate.