UI Design Basics That Developers and Founders Get Wrong

The code is clean, the features work, and the product still feels unfinished. This is one of the most common situations we are called into, and the cause is almost always the same: UI fundamentals that nobody on the team was ever taught. Designing User Interfaces catalogs them well. Here are the repeat offenders.

Is your spacing improvised?

Non-designers space by eye: a bit here, a bit there. The result never quite coheres, though nobody can say why. The fix is a spacing scale, usually multiples of 8, applied without exception. This one change does more for perceived quality than any visual flourish.

Is your hierarchy carried by color?

When everything important is a bright button, nothing is. Real hierarchy is structural: size, weight, spacing, and placement do the work, and color is reserved for the single most important action. Products built by teams without design training often have three competing primary buttons per screen, and users can feel the indecision.

Are your states missing?

Interfaces have lives beyond the happy path: empty states, loading states, error states, and edge cases like very long names. Undesigned states are the signature of a product designed only in mockups. Users meet them daily.

Is mobile an afterthought?

A desktop layout squeezed onto a phone is not a mobile design. Touch targets, thumb reach, and vertical rhythm need their own decisions.

Why does Tremoloo share this book?

Because these gaps are knowledge problems, not talent problems, and this book closes them efficiently. We recommend it to every developer-heavy team we audit.

Does your product feel unfinished despite working fine? A UX audit will show you exactly which basics are missing.