Skip to content(if available)orjump to list(if available)

Where's the AI design Renaissance?

Where's the AI design Renaissance?

72 comments

·October 16, 2025

scuff3d

> My hunch: vibe coding is a lot like stock-picking – everyone’s always blabbing about their big wins. Ask what their annual rate of return is above the S&P, and it’s a quieter conversation

Best summary I've heard so far

donpedrito

[flagged]

BoorishBears

the tone is bad, but the sentiment is accurate.

vibes coding is massively saturated with early model-access poasters who define the narrative on each release.

donpedrito

Sorry I got the tone wrong -- you are right! Simon is just normalizing sex work in tech and we should be proud.

null

[deleted]

jampa

LLMs are architected to aim toward the center of the bell curve of their training data. You shouldn't expect them to produce innovative ideas, but the upside is they also won't produce terrible ones.

The same applies to design. Most of the time, you get something that "doesn't suck", which is perfectly fine for projects where using a designer isn't worth it, like internal corporate pages. But consumer-facing pages require nuance to understand the client and their branding (which clients often struggle to articulate themselves), and that's not something current models can capture.

codyb

Internal corporate tooling can be greatly improved by promoting scheduled "water cooler chat on steroids" calls between engineers/designers/product/tpms/managers and the actual users.

What's nice is that these sessions bleed into everything. You don't need to look through users' eyes that many times to find great improvement in UX sensibilities.

Since scheduling is the biggest pain point here, I just built a scheduler and a signup form at work. Everyone who gets a session walks away with positive feedback, the company as a whole becomes more interconnected, and now I'm working to get more and more folk on board.

My goal is to unleash a whole flotilla of white collar workers who understand the value of talking to the users such that they too push for lightweight, no action item, scheduled sessions which becomes standard practice as part of our careers and we all end up with better software as a whole.

agentcoops

I think the big issue with design is the ux to LLMs at the moment: it’s really hard to iterate on a design, see the output, make changes etc. I’ve had terrible luck getting good design from ChatGPT/Codex, but V0 is probably one of the most impressive AI UX experiences I’ve encountered — I often show it to non-technical friends who are ai skeptical.

coolKid721

LLMs don't produce ideas they implement them, anyone who is relying on LLM produced ideas basically doesn't matter the whole point is they make people who want to design interesting stuff have a lower barrier to entry of actually producing stuff.

joenot443

I think this hits the nail on the head.

I've had great success using Claude to produce a new landing page which is much more stylish than something I would produce myself. It's also nowhere near the standard expected from a professional designer, but for a FOSS app, that's just fine with me :)

saulpw

> the upside is they also won't produce terrible ones.

Design by committee is known to produce terrible designs. The best an LLM can do is to completely copy a common decent design.

Espressosaurus

Yeah, my experience is that when they do work they'll get the job done but the design is going to be unmaintainable garbage unless I force my own design on it.

lysace

Tangent: Google keeps doing the same with GCP/Firebase/etc. Every year they launch a bunch of really well-crafted services that make it easy to build the most average kind of product in whatever area is trendy that year. Every year I am left intrigued but needing more to actually make use of them. The next year it's something else.

I guess this is primarily a business pattern. Or anti-pattern?

daxfohl

Assuming you mean cloud platforms in general, I don't even think it's that tangential. In fact it may cut to the heart of the matter: if React-over-REST-over-SQL-plus-some-background-jobs was all we needed, cloud platform innovation would've stopped at Heroku and Rails 20 years ago, and AI could probably make a run on replacing SWE jobs entirely.

But as it's played out, there are a ton of use cases that don't fit neatly into that model, and each year the cloud platforms offer new tools that fit some of those use cases. AI will probably be able to string together existing tools as IaaS providers offer them, perhaps without even involving an engineer, but for use cases that are still outside cloud platform offerings, seem like things that require some ingenuity and creativity that AI wouldn't be able to grok.

null

[deleted]

troupo

From time to time I look at the explore page of various AI design tools, and they are as corporate-depressing as I didn't expect them to be [1]. It's not even a bell curve. It feels like they are overindexed on bland corporate aesthetic. Getting them to output anything but a Linear clone is an exercise in frustration.

[1] https://x.com/dmitriid/status/1953750443248562431

daveguy

Is there a reason you have two of each example in your post? Or did some tool produce literally exact designs from a single prompt? If so, what tool?

troupo

It's not two of each example. It's two screenshots. One from Lovable, one from v0 :)

daxfohl

To me, the key quote is the simple "If you had told me in late 2022 I’d be saying these things 3 years later, I would’ve been pretty surprised." As someone with little exposure to the design industry, seeing how quickly AI could generate images, I'd been under the assumption that the AI takeover was already well underway there, so was surprised to learn that it's not.

If anything, that gives some comfort around the future of engineering job prospects. While there's still room to worry, "yeah but design is fundamentally human, while engineering is mostly technical and can be automated", I'm sure, just as design has realized, that when we get to a point where AI should be taking over, we'll realize that there's a lot of non-technical things that engineers do, that AI cannot replace.

Basically, if replacing a workforce is the goal, AI image generators and code generators look like replacement technologies from afar, but when you look closer you realize they're "the right solution to the wrong problem", to be a true replacement tech, and in fact don't really move the needle. And maybe AI, by definition of being artificial and intelligence (as opposed to real common sense) as a whole, is fundamentally an approach that "solves the wrong problem" as a replacement tech, even as AGI or even ASI gets created.

gyomu

That quote stood out to me as well, but mostly because the 3 images shown by the author have nothing to do with product/interface/communications design.

I guess they’re vaguely cool looking images? If the author had used them to talk about how “concept art” in games/movies was going to get upended by AI there would be a point there, but as it stands I find it very puzzling that someone who claims to teach design would use them as key examples of why design - a human process of coming up with specific solutions to fuzzy problems with arbitrary constraints - was headed in any particularly direction.

madrox

Design moves at the speed of culture; not technology. It took 3 years of people messing with mobile phones before it occurred to someone to implement "pull down to refresh" and much longer for it to be common practice that people just expect from UX. I think people are still learning what they want from an AI experience.

I do think you have to be pretty targeted with your predictions, though. Consumer product design seems to be evolving differently from B2B and at a different pace. Growth curves are different for each.

nitwit005

One of the bigger design battles at a prior company was designers insisting on pull to refresh, and the researchers insisting on removing it due to customer feedback.

lacy_tinpot

At the end of the day there's no point in trying to convince people of what they don't want to be convinced of.

Better to just show progress instead.

Back then people were similarly incredulous of the entire idea of the internet and apps.

JCM9

I think it raises the bar on what’s needed to be a designer, but I don’t think it replaces the need for a designer.

I’d draw parallels to web design. Yes some frameworks made it incredibly easy for anyone to whip up a decent looking professional site. But then 95% of websites were the same boring single page scroll nonsense with some fancy CSS. It checks a box but isn’t notable. If you hire a designer to do something truly original then you can stand out.

It will be the same with AI where “good enough to check the box” becomes easy, but going beyond that still requires skill and experience.

kingkongjaffa

The number one thing that AI is lacking is taste, precisely the reason we need designers in the first place. An engineer (most engineers are not designers) alone, or an LLM is not thinking about good design principles and doing the things needed to develop good taste.

It's the reason why LLMs are horrible at writing, and the reason why good design is really hard to get out of an LLM. Figma Make and Claude Code are really just using the out of the box CSS from shadcn that's why everything looks the same.

kingkongjaffa

on the other hand:

> After 2.5 years of insane hype, there’s no evidence that current AI is making the design process faster

I am designing prototypes faster today with LLMs this is just flat out wrong. And it's not really 2.5 years it's more like the last 6 months, GPT5, sonnet 4.0 and 4.5 have made this stuff viable to seriously use.

didibus

> I am designing prototypes faster today with LLMs this is just flat out wrong

One thing I've wondered and not been sure of, is that you can see productivity boost in parts of the process, but overall the end to end process doesn't seem to be getting done faster.

I'm not sure of this, but it's what I've observed at work.

You might be designing a lot of prototypes faster, but are you landing on something good quicker? Are you getting the final product out faster?

jmull

> it's more like the last 6 months

Perhaps it is finally true this time, but the AI hype machine has been making this very same claim for years now.

You'll have to understand if we insist on tangible results before buying that Kool-Aid in bulk.

I wonder how much of the stuff that actually takes up the time of the people we call "designers" to do their jobs is something our current crop of LLMs is good for. If it's 90% then LLMs could make you a 10x designer. If it's 10%, LLMs could make you a 1.11x designer (minus the time it takes to fiddle around with the LLM, of course).

fellowniusmonk

I've still not seen any good workflows for design prototypes, are you talking designing code prototypes or design?

levmiseri

Lots of these discussions are simplifying design to 'making things look pretty'. That's just not true for even the more visual-based design disciplines like graphic design. And the 'regular' product design (ux/ui/ixd) happening in most tech companies has very little of this compared to the rest of the scope of what a designer really does.

Product design isn't a layer that you apply. It's not an output of some prompt. It's a difficult-to-define process of crafting the interface between the user and product's functionality.

squid_fm

I’m a product designer and this is what I’ve noticed:

- When I use AI to vibe-code, it gives me a usable result but I personally have no idea if the output is “correct”. I am not sure if there are security vulnerabilities, I don’t know what is actually happening under the hood to make it work, etc.

- When my engineering friends use AI to vibe-design, I notice the same pattern. It looks “designed” but there are obvious usability issues, pattern mismatches for common user goals, and the UI lacks an overall sense of polish.

Basically, my takeaway is that AI is great for spinning things up quickly but it is not a replacement for fundamentals or craft.

Mabusto

Design is one of those things that succeeds or fails in subtlety and both are difficult to quantify and back propagate through any sort of process, let alone training a model. The same way we figured out that the microwave can make approximations to good food quickly, so too shall we see that AI can do the same with tasks that rely heavily on a connection to people's aesthetics.

Glyptodon

I'd add a #3 to the "explainable with" list: the trend towards relentlessly outsourcing work, often in situations where you get 1/2 the quality on 2x the timeline, because it's still cheaper than good engineers and the ostensible relentless time pressure turns out to not exist if offshore workers are cheap enough.

couchdb_ouchdb

"After 2.5 years of insane hype, there’s no evidence that current AI is making the design process faster"

This is antidotally untrue. I work for a small startup. We don't have the money / aren't willing to pay for a full-time designer. So, let's just say, our UI design has always been pretty terrible. With AI, using claude, to generate design and HTML / CSS based on requirements, the design that has been generated has been heads and tails better than anything we ever came up with alone.

pphysch

AI can definitely help bootstrap from Terrible -> Okay. But provides little/negative guidance on going from Okay -> Exceptional.

AaronAPU

It doesn’t lead, but it brings up to speed.

fidotron

I thought a huge part of the perceived value of ChatGPT etc. is the ability to bypass the work of designers. The whole dream of AI is not having to deal with what someone else thought the solution to your problem was, and instead just skipping to the end.

lateforwork

> After 2.5 years of insane hype, there’s no evidence that current AI is making the design process faster

This does not match my experience. I have been using Claude for speeding up design. Describe your page and ask it to use Tailwind and it will come up with some interesting designs. You still need a designer because some designs it comes up with are over the top, and need to be moderated.

jmull

I sure wouldn't start with tailwind.

BoorishBears

Most designers I've worked with don't want Tailwind slop as a starting point.

At most AI prototypes and images serve the role that a whiteboard drawing or wireframe did before: that's a win, but it's not an monumental change in efficiency.

I ironically think AI is already there in terms of being capable of more, but no one has built the right harnesses for AI.

Loose tailwind classes and shadcn is not it.