Lab Notes

The 12 Tells That Out Your App as Vibe Coded

A checklist you can run in five minutes, from a designer who scores these for a living.

July 13, 2026

A vibe coded app has a house style, and everyone in your market has learned to spot it in a second. Not because the code is bad. Because the surface wears the same twelve tells. Here is the full checklist. Run it against your app and count your hits.

The visual tells

  1. Purple to blue gradient on the hero, and often the buttons too.
  2. Inter everywhere, the default font of the AI web.
  3. Glass cards, frosted and floating, on a page that did not ask for them.
  4. 16px radius on every element, untouched since the starter template.
  5. The same page skeleton: hero, three feature cards, pricing, footer, in that exact order.
  6. Emoji as icons, because the model could not source a real set.

The copy tells

  1. A headline that could sell anything: build the future, ship faster, unlock growth.
  2. Filler verbs: streamline, empower, supercharge, elevate. The audience now reads these as slop markers, not benefits.
  3. Three feature cards of equal weight, so nothing is the point.

The structural tells

  1. No empty states, so new users hit blank screens and assume it is broken.
  2. One breakpoint, so it falls apart the moment someone opens it on a phone.
  3. No trust surface: no faces, no proof, no specifics, nothing that says a real person stands behind this.

What the count means

Zero to two hits: you made real decisions. Three to five: you are in the mild slop band, fixable in an afternoon. Six or more: your app is doing the work of convincing strangers you are not serious, before your product gets a word in.

The uncomfortable part is that none of these are hard to fix. They are hard to see, because you approved every one of them and your eye has stopped noticing. That is the trap of vibe coding. The tool that built the app in a day also handed it the exact look that gets it dismissed.

You do not need to become a designer to clear the list. You need someone, or something, that can see what you can no longer see. Run your app through auditmy.design, get the tells named and pinned to the screen, and clear them one by one.

Related