A query created by a human and reviewed by at least 1 other human becomes static after it's merged. But the query from an LLM is dynamic, it can change between two calls in the same session if the LLm sees a reason to change it, and there is no review pipeline and QA stage.
The folks at Wall Street do not understand this does not replace Figma.
Figma is targeted towards designers who create thoughtful design systems and cohesive UIs and who don't code, while this is targeted towards vibe coders who can't design. Two different circles that intersect to some level.
But like you said, if anthropic adds the tools in Figma, only then they can can take customers from Figma IMO.
>Figma is targeted towards designers who create thoughtful design systems and cohesive UIs and who don't code, while this is targeted towards vibe coders who can't design. Two different circles that intersect to some level.
The challenge is that this sets an expectation of what "design" is, de-valuing the former and shifting us culturally towards the latter and a space where "design" is seen as a subjective visual exercise with little intrinsic value.
I think there's a parallel here in advertising and what AI has done there. It's clearly used nowadays, a seasoned user can probably spot it straight away even if it gets harder over time. Still, it's deemed "good enough". The savings versus having a team and shooting on location etc. can be enormous. Even before this launch, I see it on the web. It's already happening.
Tools like Figma are for an era (and persona) who still wants to have all the various knobs and dials to dial in exactly what they want. And that is one way of working if, like you said people are trying to be more thoughtful and know exactly what they want.
But for the other 95% of people, being able to just say "ok can you make it look more modern" and have 4 variants in 5 mins, (like me) Figma will lose users like me.
But then again I was never a "designer" – more a builder.
> But then again I was never a "designer" – more a builder.
Same here. I work in Claude Code all day long on slightly complex b2b apps, and the builder MVP for what I want to do with Claude.ai, to work on ideas is far simpler.
I just want to be able to create a React artifact prototype on claude.ai, then share it privately with a stakeholder (internal or external.) I want to allow those users to prompt changes, then see their changes in the artifact.
The bespoke design is not what I am really worried about at this phase. For b2b prototype stuff, claude.ai already does an excellent job with just a bit of project-specific prompting.
Why is this shared artifact building not yet doable? This seems "so simple." Yes, maybe some shared artifact specific git to allow version control is required, but is my ask really that hard, or unique?
I'm much closer to your persona than a professional designer. 5 years ago if I was going to spin up a landing page for a side project I was probably getting something mediocre together with bootstrap or material UI. Today I'd probably get something marginally better together with a tool like this. In both scenarios I'd end up with an undifferentiated but acceptable end state.
I've never paid for a figma seat. A couple of employers have so that I can collaborate with designers in the product, but I don't think this changes that.
In an era where it's cheaper and more common to end up at that undifferentiated state, the ability for companies to make their products go above and beyond it is more valuable, not less.
I see this across the board with AI. It lowers the bar to get to passable, but as slop fills the internet we're already seeing people place more value in good products, good writing, good art, thoughtful code architecture, etc. Everyone and their cousin's uber driver is vibe coding a SaaS startup no one's going to pay for right now.
Ah, slopper is hilarious. Too long has the title of builder just been an excuse to make dog shit UI and excusing yourself. If you're going to build user-facing tools, good UI/UX is a requirement not an option. Couldn't imagine this excuse flying in any other industry. Yeah I just made a chair where all 4 legs are different lengths and the back rest is in the middle of the seat, "I'm just more of a builder"
Would you like to attempt a more good faith interpretation on what I meant, and address that (you can even imagine doing this in front a user/client and iterating in minutes with them, ultimately getting even better outcomes), instead of inventing the most un-generous interpretation of what I said, that I'm just adding AI slop?
> > But for the other 95% of people, being able to just say "ok can you make it look more modern" and have 4 variants in 5 mins, (like me) Figma will lose users like me.
This does not describe thoughtful, good work. At best, this will be a one-armed bandit deal where you're gambling on something good in these 5 minutes. It sure sounds like a scenario where you will mostly accidentally end up with something good.
I don’t think I can interpret it in better faith. You’re excusing low quality output by calling yourself a “builder” (meaningless term btw), is “slopper” not an accurate term here? How else would you describe somebody who spends 5 minutes prompting an LLM on one of the most important aspects of a product?
Everyone who creates something is a “builder”, that term doesn’t excuse someone from not putting effort in. I don’t care if you aren’t a designer, it’s about the effort you put into your work :)
The obvious bad faith part of your argument is assuming that it's "low quality output." Another is using a blanket negative and dismissive term like slopper, without taking a chance to actually see the work output (at least in my case).
You also clearly misread what I said. I didn't say I spent 5 minutes prompting an LLM. I say the ability to get FEEDBACK (a revision) in 5 minutes is amazing. And I stand by that. That allows me to do 20 more revisions and do in a couple of hours what would take two weeks.
You seem to be romanticizing the concept of grunt work – that for something to have value or be of good quality, you have to put in some sort of minimum amount of time on it, and it has to be tedious. It's the same concept that nobody can make a good quality piece of furniture unless they used a hand saw and spoke sweet nothings to the tree before it was cut.
There are ways to do things quicker while preserving quality. I had already left a caveat saying that for the 5% of people that really want to push web design forward, totally, go ahead. But for the rest of us (including those of us who have lived and breathed code and engineering principles for decades), these tools are phenomenal for iterating quickly.
Anyway, the term builder is more about separating the goals from a vanilla "programmer" - even though i've programmed my whole life, it's always been in service of an outcome. And the outcome is almost never "good code for the sake of good code" - it has to serve a real outcome in the real world.
By the way, lots of good designers are also using coding agents now, so you can keep romanticizing grunt work while most of the market moves on.
> But for the other 95% of people, being able to just say "ok can you make it look more modern" and have 4 variants in 5 mins, (like me) Figma will lose users like me.
Perhaps this phrasing is what invited the interpretation you seem to be annoyed with.
There is not much to gain by suggesting everyone is simply bad faith.
No the bad faith part comes from assuming that the output is low quality, and that just because I get _feedback_ in five minutes (read again what I said) it somehow implies that I spent 5 minutes on it and then moved on, never to revisit.
I think you like the other person is assuming that 5 minutes = low quality. Instead of thinking "5 mins means you can make 8-10 iterations in an hour" or "5 minutes making the front end look pretty good means I can spend more time on the backend"
There are many ways to interpret this, yes. I only mean to disrupt the framing you keep asserting of good and bad faith, I'm still not sure I understand what you are getting at.
No one is assuming the output is strictly low quality from what I can tell. I am personally evaluating the method you provided, which suggested you are championing a sloppy but highly iterative design flow against a seasoned curated suite for defining design. I dont see any reason to assume the other comment was doing anything otherwise.
You made a broad generalized strong claim and were met with the opposing force, which is actually acting from their own understanding of good faith, believe it or not (see how this analysis is void of meaning?).
This take might have sounded convincing a year ago. Now it just sounds foolish. The best coders on the planet are using AI. Why wouldn’t they use this?
"Use AI" sounds like "programmers use a machine that can be programmed to automatically carry out sequences of arithmetic or logical operations" - without the details or context how they use it, what tools and for what tasks - doesn't mean anything and also sounds foolish, sorry.
It probably reduces the tasks which customers might engage an agency using Figma, though. Down the line, creeping onto Figma’s turf absolutely becomes a strategy for Anthropic.
> Figma is targeted towards designers who create thoughtful design systems and cohesive UIs and who don't code, while this is targeted towards vibe coders who can't design. Two different circles that intersect to some level.
this overlap has been widening incredibly quickly. lots of designers are now writing code with the help of cursor, claude code, etc.
even if you believe "real designers" wont ever use this product, it's not hard to see how a low barrier-of-entry tool could affect Figams bottom line. slowing down Figma's adoption from the new wave of entry-level designers who dont already have muscle memory would not at all surprise me at all.
The bulls' theory is that right now the person who doesnt know how to design pay a designer that will use figma, but with something like claude design they can just vibecode the thing without having to get a designer involved.
Its making alot of bold assumptions, but we live in interesting times so thats par for the course
Design systems are a means to an end. They’re as much about enabling delivery without requiring a designer to design every feature from scratch each time as they are about ensuring cohesive overall design. I can see this being a viable alternative path to the first if you’re happy with a slight hit to the second.
I think they understand that the people running businesses are going to look at this vs a human who uses Figma and realize how much more cost and time efficient it is to pay for a machine than a human.
As with anything, it depends on the quality and skills of the people doing the designing. I have yet to really work with a designer that embedded themselves enough in the UX to design anything I thought was good.
Granted, I have not worked with that many designers so it’s maybe small N problem.
The gap between figma and where our front end teams work and design is still too large.
I think the more likely result of this is fewer designers and more work for developers with some design skills.
I'm not sure they don't care anymore, as much as they experienced the same pressure every company faced when AI went mainstream.
Had they not included support for it, where would they be now? I'd wager a critical mass would be screeching to High Heaven for integrations, seeing as a Figma document is effectively a config file that can be translated to real code.
Figma was never needed. they were useful when enterprises allowed people with no coding experience to mandate how ui should look. It is the powerpoint of dumb people that wanted a career in tech. happy to see it dying.
Hard disagree. There's more to UX than pushing pixels around. Usability, accessibility, and capturing the broader customer experience at 40,000 ft isn't a trivial process when you're designing a large product (or suite of products) especially.
These areas obviously tie into engineering very closely, but the thinking that goes into them happens at the design stage, at a lower cost than starting with engineering. AI models suck at getting every facet of this process right, because designers are achieving a balance between branding, usability, standards, taste, and differentiation -- the exact opposite of a model trained to reach for the most average outputs.
My SO is a UX designer and uses Figma. She wanted to try out Claude integration there, but was frustrated by limitations - like why she can't export interactive elements to Figma file format so that they can be edited further.
So I helped her look into it and I was shocked to find out that it just a react slop generator, not a Figma file generator. And extremely limited at that, too.
Who is Figma targeting with this exactly? Developers, who are interested in react apps will simply use claude code, and UX designers don't really care for react apps.
I think the target market for this is small businesses wanting to throw together quick concepts without needing to hire a contractor necessarily. This smells more like Squarespace and what they did for brochure websites / portfolios than anything else, but perhaps more general purpose.
Just last week, I asked the designer on my team to try working in Codex instead of Figma. It’s just not a great workflow to pass a figma file to a developer to implement. She hasn’t wanted to go back yet…
100% this, Figma is more than just a "design" tool. Same as jira is not just a crud app for tasks. It is integrated in pipelines, people's expertise, CVs and CTO's minds. And to bet on AI company building a competitor to Figma - good luck with that. Just a pilot project for PR, nothing more than that. Sora 2.0 basically.
Not sure what the technical challenge here is either. I use an ad blocker and I assumed YouTube already counted my view, since the video can be found in my YouTube history.
I imagine watch history view tracking and view count view tracking and possibly even ad impression view tracking are three disconnected systems. Google is still going to update your history view even if it thinks you're a bot so you don't know you're being filtered out for example. The data to power that UI can also be partitioned by user while the ad and view count data needs to be aggregated performantly across large numbers of users in different slices. On the other hand your watch history doesn't keep multiple entries if you watch the same video multiple times in a day (say a music video on loop) but does want to charge for each ad impression seperately.
I think it has to with the audience, or a platform. A young farmer would probably pretend to know a lot and even talk to impress if you put an audience in front of them.
It depends on the browser you're using, Brave is obfuscating a lot of this info, for me using Brave on Android it shows 100% battery while my actual battery is 62%.
reply