AI's UI slop is taking over the web, and it's painfully obvious

10 Tells of a Slop UI

AI's UI slop is taking over the web, and it's painfully obvious

A college app update, ironically billed as "minor UI improvements," exposed the telltale signs of AI-generated interfaces. From pointless pulsing badges to purple gradients and redundant text, these design choices scream "vibe-coded" and make apps look cheap. The author catalogs ten recurring patterns—like glassmorphism, emoji spam, and generic taglines—that plague LLM-crafted UIs and argues that a lack of human effort is to blame.

It treats every screen like a landing page rather than a functional tool.
  1. weakfish

    I’ve been trying to put my finger on what it is that is happening when the robot writes stuff like “3 campuses, one app” example, I’m glad the author was able to identify it as chat context leaking through.

    The other version of it is the robot over-indexing on some part of the prompt and leaving comments places. An example is I ask it to prefer integration tests using TestContainers, it starts adding comments to every new test saying “Real services, no mocks” or something.

    And yes, I have a line in my *.MD saying not to do that.

  2. czhu12

    At least some of these are just for lack of caring. I vibe coded this landing page recently https://tui2web.com/ and fought off a lot of the defaults the LLM came up with after a few hours of iteration. Feel free to roast it, I'm not really attached, but I thought it did a reasonably good job.

  3. vallerie

    Love this blog mentioning the issue of implementation detail in prose. Likely my biggest irk of vibe coded apps.

    Much of this is it's a simple problem to solve - just prompt agent of choice "Put all user visible text into a translation file for i10n" and then go through and edit said prose as a human.

  4. zinoc

    This is similar to the rapid early adoption of the Bootstrap CSS framework. A lot of people were annoyed by the sudden spike of websites that looked and felt the same, but I think this was a tremendous step forward in usability and accessibility, and well worth the initial wave of cookie cutter websites.

  5. tptacek

    An "inactive" student is one who is enrolled but is not currently attending classes.

    This is a super useful article but a lot of these complaints about things like alignments are also the natural outcome of me, a non-frontend person, building any kind of web frontend at all. So I wouldn't sweat it too much.

  6. jph

    I start with these rules, then adjust as I want...

    EMPHASIZE:

    - *Summary.* First paragraph like newspaper (who, what, where, when, how, why).

    - *Benefits.* Focus on the benefits for the reader.

    - *Why this matters* Focus on what it adds to the reader.

    NO:

    - *No tech stack.* Do not say the tech implementation; covered elsewhere.

    - *No counts.* Do not say page counts, part counts, chapter counts, etc.

    - *No special formatting.* Do not bold, not italic, not bullet lists.

    - *No "if".* Do not say "If you do X then Y"; instead use positive.

    - *No run-on sentences.* Do not use many clauses nor too many words.

    - *No passive voice.* Do not use passive, or non-subject, sentences.

  7. mjr00

    The most important thing I learned when graduating from "bad musician" to "passable musician" (passable enough to have listeners and fans, at least) was that there's no one single big trick that turns a song from bad to good: there's 100 tiny small tricks that add up. And you need to have experience to know what they are. A trained listener might be able to say "the midrange is too compressed", "there's too much high end", "the drum transients are't punching through", but a normal, casual listener is just going to say, "I dunno, it just doesn't sound right."

    This UI slop is the same deal. A slightly misaligned dot off the timeline, color choices which don't really make sense given the website as a whole, using LLMism text. Nothing in here is an obviously major problem on its own. But when you add up 50 of these on a website, users get hit with that "this is slop" feeling.

    The details matter. In isolation they seem irrelevant, but as a whole it's what elevates something from the AI slop garbage pile to something actually good.

  8. docheinestages

    I just can't fathom how a multi-billion dollar company like Cloudflare could forego their design standards. They seem to have updated their landing page [0], but it's still very sloppy.

    [0] https://try.cloudflare.com

More from this day

2026-09-27