> Quoting from the article, which of course you did not read
What makes you think that I didn’t read the article, but rather just disagree with it?
“which of course you did not read” is such a negative/toxic statement that adds no value.
obviously developers use the product to collaborate with designers. but it’s not the developers that are buying this product. they’re just stakeholders.
The developer seats are read-only, so they rely on designer seats existing to actually create files to inspect for development (and I’d guess PMs are using figma because designers are using figma).
If designers still want Figma then the other people are along for the ride (unless the idea is the designers are being replaced with a PM+Claude.)
As a PM in a startup, it took me a while to convince my boss I’m not a designer. It’s so easy nowadays to get a Figma file with an established design system and produce new features.
There are Figma plugins that let you extract a static HTML website into a Figma file. Copying that over Figma Make and prompting for a while can make pretty good prototypes that need very little adjustment back in Figma.
However, I believe that being able to do something doesn’t mean you should do it. Prompting back and forth can easily introduce a lot of cognitive load on top of all sorts of other daily task.
I feel the modern human in the loop is similar to the factory processing line workflow where just almost anyone can learn how to use a tool and produce output.
A very large portion of the non-design users are using it to reference/implement the designs created by their designer colleagues. They’re not going anywhere.
Sure, if your design decisions are completely one-sided and transactional. In my experience, though, being able to comment and collaborate in Figma is important, as is being able to go find specific icons and components on my own.
> Quoting from the article, which of course you did not read
What makes you think that I didn’t read the article, but rather just disagree with it?
“which of course you did not read” is such a negative/toxic statement that adds no value.
obviously developers use the product to collaborate with designers. but it’s not the developers that are buying this product. they’re just stakeholders.
The developer seats are read-only, so they rely on designer seats existing to actually create files to inspect for development (and I’d guess PMs are using figma because designers are using figma).
If designers still want Figma then the other people are along for the ride (unless the idea is the designers are being replaced with a PM+Claude.)
As a PM in a startup, it took me a while to convince my boss I’m not a designer. It’s so easy nowadays to get a Figma file with an established design system and produce new features.
There are Figma plugins that let you extract a static HTML website into a Figma file. Copying that over Figma Make and prompting for a while can make pretty good prototypes that need very little adjustment back in Figma.
However, I believe that being able to do something doesn’t mean you should do it. Prompting back and forth can easily introduce a lot of cognitive load on top of all sorts of other daily task.
I feel the modern human in the loop is similar to the factory processing line workflow where just almost anyone can learn how to use a tool and produce output.
Personally, as a developer, I interact with figma to use designs made by designers. So a portion of that userbase probably isn't going anywhere?
A very large portion of the non-design users are using it to reference/implement the designs created by their designer colleagues. They’re not going anywhere.
if you export the .fig file (even programatically) and you ingest in Claude Design you won't need to create users in Figma, right?
Sure, if your design decisions are completely one-sided and transactional. In my experience, though, being able to comment and collaborate in Figma is important, as is being able to go find specific icons and components on my own.
1 reply →