UI

The interface layer users directly see and touch: layout, components, typography and visual design of a product.

User interface is the concrete surface: screens, buttons, forms, typography, spacing, color and the components they compose into. Where UX is whether the flow works, UI is what the flow looks and feels like at every step. The line matters in practice: a beautiful interface over a broken flow fails, and an efficient flow behind a chaotic interface never earns the trust to be tried.

Why it matters to an indie builder: interface is the first thing a visitor judges, in the first seconds, and for a self-serve product it is effectively the sales pitch. Consistency is the force multiplier available to small teams: a coherent component set makes every new screen cheaper to build and simultaneously easier to use, which is why design systems punch above their weight at this scale.

A concrete example: a settings page assembled from mixed sources, a date picker from one library, toggle switches hand-rolled, a table from another kit. Each works; together they imply three different products. Replacing them with one component library, Tailwind plus shadcn/ui in the React world, cuts the page's build time by half and, measured in support tickets, removes a steady drip of users who could not find the toggle they needed. The consistency paid for itself before the aesthetics did.

Common mistakes: chasing novelty in layout when conventions (top nav, left sidebar, table plus detail) are what users already know how to operate, inconsistent states (a button that looks identical whether disabled, loading or active teaches users to distrust every button), low contrast text in the name of taste, and skipping empty and error states, which are exactly the screens users see when something went wrong and when they most need clarity. The ui trait blocks on IndieBoot point to component libraries and design tooling worth borrowing from.