People Hate AI Art — and the Signal Matters for Builders

The hostility toward AI art is well-documented at this point. The post at mccue.dev frames it directly: people hate AI art. Not all people, not in every context — but the pattern is consistent enough that engineers building AI-assisted products should treat it as a hard constraint rather than a PR problem to route around.

The practical implication is about surface area. AI-generated visuals are a visible, legible artifact of AI involvement. They trigger a reaction that text outputs often do not. When a product uses AI art — in marketing, in UI, in generated content — it surfaces the AI in a way that invites rejection before the underlying utility can be evaluated.

For solo founders and small teams shipping fast, this matters at the product-decision layer. Swapping in AI art to cut costs or move quicker on visual assets is not a neutral tradeoff. It carries social cost that compounds if the core user base is already skeptical of AI-assisted workflows. The artifact becomes a proxy for trust, or the absence of it.

There is also a more structural point. The art backlash is partly about labor displacement and partly about aesthetic flatness — outputs that feel generic because they were optimized for prompt-response plausibility rather than craft. Engineers building generative tools should understand this distinction. Outputs optimized for plausibility tend to converge toward the median. That is useful for some tasks and actively harmful for others, particularly anything where distinctiveness or credibility is the product.

None of this means AI-generated imagery has no place in a build. It means the tradeoff needs to be deliberate. The mccue.dev piece is worth reading as a calibration exercise — the audience reaction it describes is the same audience using the tools you are building.

Source