User interface (UI)

The part a customer actually touches

Every website is two things: what it holds, and how that gets presented. The interface is the presentation. Menu bars, headline sizes, the color and shape of the quote button, the width of a form field, what a link looks like once it has been clicked. All interface.

Good interface work goes unnoticed. Nobody compliments a button, they press it. You notice an interface when it fails. Two buttons that look equally important, so neither reads as the main one. A phone number styled as plain text, so on a phone it does not look tappable. An error message that appears above the part of the form the visitor already scrolled past.

Interface also includes state: what a button looks like while it is being pressed, what a field looks like when it is wrong, what the menu does when it opens. States are where cheap builds tend to stop, and where a site starts feeling untrustworthy without anyone being able to say why.

Consistency does most of the work. If the quote button is one color on the homepage, it is that color on every service page. Visitors learn a site in a few seconds, then run on that memory for the rest of the visit.

What the interface decides on a small local site

On a seven page site for a trade business, the interface has one real job: make the next step obvious on a phone held in one hand. A tappable phone number in the hero section. The main action above the fold rather than below three paragraphs of company history. Text sized so a 60 year old reads it without zooming. None of that is a matter of taste. It is a matter of what a thumb can hit and an eye can read.

Those choices have to survive every screen, which is what responsive design handles: the same interface reflowing from a laptop to a phone without shrinking a button to the size of a pea.

Interfaces are not only for customers. A one-tap review-request tool built for a New Jersey glass and mirror shop is an interface for the owner, and so is a job board for a Philadelphia staffing agency where the owner posts openings from her phone. When the person running the business finds the screen annoying, the tool stops getting used, and a tool nobody uses may as well not exist.

Interface decisions belong in the build rather than bolted on afterward, which is part of what custom web design covers.

Interface, structure, and the visit itself

Three words get used interchangeably and should not be. Information architecture decides what exists and where it sits. The interface decides how that shows up on a screen. User experience is what the person goes through when the two meet.

You can put a clean interface over a bad structure. The site will look fine in a screenshot and still send people back to the search results, because looking finished and being usable are separate achievements.

The useful order is structure, then interface, then measuring what the visit actually does. Skipping straight to the interface is how a site gets rebuilt twice, once for the look and once for the structure nobody settled.