You don't need to be a designer to deliver a decent interface. But you do need to stop treating UI as "put the components on the screen and move on." Most bad screens aren't ugly because of a lack of visual talent — they're confusing because they lack intention. Below are five habits any developer can adopt today to solve most problems before a designer needs to get involved.
Visual hierarchy: tell the eye where to look
Every screen has one most important thing. The primary action button, the number that matters, the next step. If everything has the same weight, nothing does. Use size, color, and space to tell the eye the order in which to read.
In practice: one strong primary button, with secondary actions kept subtle. A large heading, with small, gray metadata. Don't paint five things bright red and make them compete for attention. And respect whitespace — it isn't wasted space; it's what separates groups and creates breathing room. Group related elements together and keep unrelated ones apart.
Immediate feedback: a dead screen is a bug
The user clicked. Now what? If nothing changes on the screen, they'll click again or assume something broke. Every action needs a visible response in less than 100 ms — even if it's just the button changing state.
Hover, focus, active, disabled: these four states aren't a detail; they're the conversation between the interface and the user's finger. When saving, show a spinner on the button itself and disable it to prevent duplicate submissions. Did it work? Confirm it. Did it fail? Say so. Silence is the worst response a UI can give.
Consistency: predictable is a compliment
If the save button is green on one screen and blue on another, you're making users relearn your product on every page. Consistency is what makes an interface feel trustworthy even when users have never seen it before.
Standardize the obvious: spacing, font sizes, corner radii, colors, and button labels. "Cancel" should always be in the same place. Dates should use the same format. Use tokens or variables instead of hardcoding #3B82F6 in twenty places — when the pattern becomes code, consistency no longer depends on your memory. Predictability is tedious to implement and great to use.
Accessibility isn't decoration
Accessibility isn't a favor for a minority — it's what makes your UI work with a keyboard, a screen reader, or bright sunlight shining on a phone screen. Much of it is inexpensive.
The basics already go a long way: sufficient contrast (aim for AA, 4.5:1 for text), never communicate state through color alone, use truly semantic HTML (button is a button, not a div with onClick), add a label to every input, provide alt text for informative images, and ensure visible focus for people navigating with Tab. Run Lighthouse or axe once and you'll be surprised by how many issues can be fixed in a single line.
Loading, empty, and error: the three states you forget
Every developer designs the full screen, with beautiful data coming from an API that worked. Users live in the other three states — and those are precisely the ones nobody designs.
Loading: don't leave the screen blank. Use a skeleton or spinner, and avoid layout shifts when the data arrives. Empty: a list with no items isn't an error; it's an opportunity — explain what the list is for and how to create the first item instead of showing a void. Error: speak like a human. "Couldn't load this. Try again?" with a button, not a stack trace or a generic alert. If you only code the happy path, you've delivered half a screen.
The minimum that separates a good screen from a painful one
None of these five points requires artistic talent. They require intention: one thing in focus, a response to every click, patterns that don't change, contrast anyone can see, and the three states you usually forget. Do just that and your UI already moves up a level — a designer is for polish, not the basics. And the basics are what users feel first.