I’ve been thinking about this a lot lately while evaluating our own product. It’s easy to point at visual polish clean typography, nice spacing, a cohesive color palette and call it “good design.” But I keep noticing that some web apps just feel better to use even when they’re not necessarily prettier, and I can’t always articulate why.
A few things I’ve started paying attention to:
How the app handles different user roles. Admin, regular user, guest does the interface actually adapt to what each person needs to see and do, or is it one generic layout stretched across everyone?
What happens in the edge cases. Empty states, error messages, loading states a lot of apps nail the “happy path” but fall apart the moment something goes wrong or there’s no data yet.
Consistency across screens. Not just visually, but in how interactions behave. Does a button always do what you’d expect based on how it looked on the last screen?
How much friction there is in common workflows. Sometimes a design looks great in a screenshot but takes six clicks to do something that should take two.
I’ve started looking at how established web app design teams break down their process a lot of them treat this stuff (role-based flows, state coverage, design systems) as core deliverables rather than an afterthought, which honestly reframed how I think about design quality. It’s less about how it looks in a mockup and more about how well it holds up once real users with real messy data start using it.
Curious what others here think separates the two. Is it mostly about process (research, testing, iteration), or is some of it just experience having seen enough patterns to know what breaks at scale?
