Thoughts and feelings around Claude Design

How is it a leading question?

>A leading question is a query that suggests the desired answer or puts words into a witness's mouth, often guiding them toward a "yes" or "no" response.

Basic web development is completely over, and will be automated end to end, product, ux, design, and the code.

I have a complicated nextjs webapp, and I havent had to write front end code in six-nine months now.

So let me get this straight (Pretend I'm 50, a developer since childhood, but I can't CSS to save my life) are there shops where developers, even front end developers, have to talk to designers who are't just sketching an idea for a logo or landing page, but designers who run this Figma thing and maintain the entire products "design" in some "style database"? And the idea is that these designers - who aren't developers - should be able to tweak the look of things without changing code? Or is it usually just the front end devs that run this Figma thing, but they dislike the disconnect between it and their code?

The article makes a good point about how Figma's non-open data model is limiting their utility as the source of truth.

But I think it's part of a larger mistake Figma is making: they seem to have shifted to an extraction mindset too early, assuming they'd captured the market, right when the ground beneath them is starting to shift.

It's most visible in their pricing model evolution, which is now explicitly anti-collaboration. Figma used to be the obvious default because you could quickly share files with non-designers, so they could view and make small edits without fuss. Now that requires a paid "seat", along with a confusing mess of permission flows.

It's platform wide too. I taught a college design class recently, and had students sign up for Figma because it seemed archaic not to teach them to use it. Instead of just giving any ".edu" address a free account (like they used to) students are forced through a 3rd-party process of uploading transcripts to prove education status. A few of my students got rejected or ran into confusing errors, and never got access… Now I have to re-evaluate whether its worth using when teaching the class again. (And this is for a population with near-zero short-term purchasing power, but huge potential long-term value… why add barriers?)

This is such a weird self-inflicted wound for a collaboration platform to make. The big tools that won on collaboration (eg. Google Docs, GitHub) have understood that low-friction sharing is critical to becoming the default choice. And that being the default is a flywheel that drives adoption, both in users and in tooling.

It makes more sense if you see it through the lens of Figma trying to juice short-term numbers for their IPO. But it's sad to see because it had so much long-term potential.