The anti-slop field guide

"Slop" is what we call the look of software made without care — interfaces that could belong to any product because they belong to none. It isn't ugly, exactly. It's generic. And it has a recognizable face, because it comes from a recognizable place: the path of least resistance. Reach for the default component, the default font, the default gradient, the stock layout, and you arrive at the same place as everyone else who reached for the same defaults. The tools have gotten good enough that the average is now very average, and getting more average by the month.

The fix is never "more design." It's noticing the reflexes and refusing them. Here's the field guide we actually use — the tells we look for, and what we do instead.

Type

The tell: Inter (or the system font) on everything. Inter is a beautiful typeface that has been used so universally it now reads as "no decision was made here." Same for defaulting to San Francisco, Roboto, or Arial. The fix: choose a face with a point of view, and pair a distinctive display with a clean body. The right font for a "technical" product is not automatically a sans, and the right font for an "elegant" one is not automatically a serif. Pick for the brand as a physical object — a lab manual, a museum caption, a hand-painted sign — not for the category cliché.

The tell: gradient text. A headline filled with a purple-to-blue gradient is decoration pretending to be emphasis. The fix: solid color. If a word needs to stand out, use weight, size, or a single accent — meaning, not a paint effect.

The tell: setting long passages in all caps because it looks "designed." The fix: reserve all-caps for short labels. Sentence case for anything you expect a human to read.

Color

The tell: the eight-color palette. A primary, a secondary, a success, a warning, an error, an info, and two greys — all roughly equal in weight. It looks complete and feels like nothing. The fix: one accent, rationed. Accents work because they're rare. Spend 60% of your surface on a neutral, 30% on text and structure, and 10% — at most — on the one color that means something.

The tell: pure black on pure white (#000 on #fff). Nothing in the physical world is pure black or pure white, and screens that pretend otherwise feel clinical. The fix: tint everything, even slightly, toward a single hue. A near-black with a hint of warmth and an off-white to match reads as considered before anyone can say why.

The tell: dark mode with glowing accents, reached for because it "looks cool" without requiring a single real decision. The fix: earn the dark. Dark is correct when the context is dark — late-night reading, a focused tool, a cinematic register. If it's just there to look premium, it doesn't.

Layout

The tell: the three-column feature grid — three identical cards, each an icon, a heading, and two lines of text, repeating down the page. It's the single most common shape in software marketing and it says "template." The fix: vary the rhythm. Not everything is a card. Let some things be bigger, some be a list, some be a single sentence alone on the page. Sameness reads as automation.

The tell: an icon in a colored circle above every heading. They almost never add information; they add visual noise that makes the page look stamped from a kit. The fix: delete them. If a section needs a heading, the words are the heading.

The tell: the side-stripe border — a callout or card with a 4-pixel colored bar down its left edge. It is the most overused "design touch" in dashboards and it never looks intentional, no matter the color. The fix: a full border, a background tint, a leading number — or nothing. Reach for a different structure entirely.

The tell: center-aligning everything. Centered text is the safe default and it flattens hierarchy. The fix: left-align by default and use asymmetry on purpose. Centering is for genuine emotional peaks, not for every block.

The tell: the hero-metric template — a giant number, a small label, three supporting stats, a gradient behind it. The fix: only show numbers that are true and earned. A made-up "10,000+ happy users" is worse than no number; it's the first thing a careful reader stops believing.

Motion

The tell: bouncy, elastic easing on everything. Real objects decelerate; they don't spring and wobble. The fix: ease-out curves and short durations. Motion should explain a change — where something came from, where it went — not perform.

The tell: animating everything, so the whole page shimmers on load. The fix: one well-orchestrated moment beats a dozen scattered micro-effects. Pick the screen's one transition that matters and make it perfect.

Words

The tell: copy that restates itself — a header that repeats the heading, an intro that summarizes the section it introduces, a button labeled "Click here." The fix: make every word earn its place. If a sentence tells the reader something they can already see, cut it.

The tell: error messages written by the database. "Error 500." "Something went wrong." "Invalid input." The fix: write the unhappy path like a person who is sorry. The error state is where users decide whether anyone was home when the software was made.

The real test

You can memorize this whole list and still produce slop, because the list is just symptoms. The cause is upstream: treating the look as the last thing instead of the first. Every item here is what happens when a decision got deferred to build time and filled in with a default. Avoiding slop isn't a coat of polish at the end. It's deciding the thing on purpose, early, when the decisions are still cheap — which is the whole argument for treating design as the specification.

There's one test that catches everything the checklist misses. Show the screen to someone and ask: could this belong to any other product? If the honest answer is yes, it isn't finished — it's just the average, and the average now has a name.