Live data from Hacker News

Thoughts and feelings around Claude Design

samhenri.gold

231–240 of 253 posts

Re: Thoughts and feelings around Claude Design

#231
post #166

Earlier quoted context omitted.

> The big tools that won on collaboration (eg. Google Docs) have understood that low-friction sharing is critical to becoming the default choice. Google docs is a heavily subsidized product and not representative. Also tool pricing seems hard, but I can’t really get behind saying that a company should bait and switch with their pricing models harder.

Under that logic is a free trial a bait and switch? How about a 1-month free deal? How about what Adobe (and many others) do where they license to the school and students get it free until they graduate? It seems like a really weird point to make, when you could just as easily argue that Figma giving their services for free to students is a gift that levels the playing field, by allowing students without means to gai…

> Under that logic is a free trial a bait and switch? How about a 1-month free deal? How about what Adobe (and many others) do where they license to the school and students get it free until they graduate?

No. The key difference being transparency. You know when signing up for a free trial what the actual long term costs will be and can plan for it.

We might be talking about different things. I was mostly replying to this line from the OP:

> But I think it's part of a larger mistake Figma is making: they seem to have shifted to an extraction mindset too early

I’m not sure if this was just awkward wording that seems to condone these type of strategies.

All these loss leading, vendor lockin strategies have distorted markets heavily. Complex tools cost a lot of money to develop; and if another player is just going to burn piles of cash from elsewhere to undercut you, it becomes a game of capital allocation and not individual product quality/costs. It’s terrible for consumers and a big reason why even common chat apps are barely functional.

Re: Thoughts and feelings around Claude Design

#232

Earlier quoted context omitted.

Good design is distinctive. No one wants a world where everything looks the same.

If I’m buying art for my wall, I want variety. If I’m slamming the brake pedal in a car, I want consistency. Too much software in the latter thinks it’s part of the former.

A hammer should look like a hammer, a saw should look like a saw.

Re: Thoughts and feelings around Claude Design

#233

Earlier quoted context omitted.

That’s because designers stopped caring about following each platform’s guidelines because they want to spread “brand recognition” or some shit like that.

This is kind of a revisionist view of software. I think most of the consistency we remember from software past is because skipping the OS tollboxes and doing your own custom UI was hard rather than because most software developers cared about consistency. Yes the OS vendors did, but one doesn't need to go far to find applications that very much did their own thing. "Bubbly" and "goopy" UIs of the sort "Kai's Power To…

At least in the goopy days it was VERY clear what was and was not a button.

Re: Thoughts and feelings around Claude Design

#234

Earlier quoted context omitted.

> only it was "Photoshop files hold the (design) truth" before You mean Fireworks. Photoshop was for graphic design. Web designers used Adobe Fireworks. Figma is a successor to Fireworks, not Photoshop.

Nah yeah Photoshop .PSD's were totally normal for website designs. I got extremely proficient at building functioning websites based on PSD files, going back as far as the days of using nested structures with 1x1 transparent spacer.gif images :) I built hundreds of websites from .PSD files, and Fireworks was pretty much non-existent in my experience.

Yeah +1, at the start of my career (mid 2000s) all the web designs were done in Photoshop. I think this was true until 2010/11 at least, when I first encountered Axure being used for some design stuff. I’ve never used Fireworks and never saw it in the wild (UK, in case it was a regional thing)

Re: Thoughts and feelings around Claude Design

#236
post #231

Earlier quoted context omitted.

Under that logic is a free trial a bait and switch? How about a 1-month free deal? How about what Adobe (and many others) do where they license to the school and students get it free until they graduate? It seems like a really weird point to make, when you could just as easily argue that Figma giving their services for free to students is a gift that levels the playing field, by allowing students without means to gai…

> Under that logic is a free trial a bait and switch? How about a 1-month free deal? How about what Adobe (and many others) do where they license to the school and students get it free until they graduate? No. The key difference being transparency. You know when signing up for a free trial what the actual long term costs will be and can plan for it. We might be talking about different things. I was mostly replying to…

That's fair. I'm also heavily opposed to VC-funded, market-distorting behaviors and the later extraction-oriented outcomes they produce. In this case I was framing it in terms that might be more widely received by folks who aren't, and pointing out that, even if that was their mindset and goal, they were still making a mistake strategically.

But I appreciate the reminder to not cede ground in wording, thanks.

Re: Thoughts and feelings around Claude Design

#237
post #23

Earlier quoted context omitted.

It was just restating what you already said; no need for this specious response.

Please quote me where I said 'my designers debug react code that AI messes up.' I did not say anything of the sort. See also: https://news.ycombinator.com/item?id=47819428

"Debug react code" => "Front-end"

"Designers" => "Design"

>Front-end, UX, design, and product have become one role.

Ok so, are your "designers" (now part of one role) not debugging react code? If they are then you mislabeled the question as leading to avoid discussing in good faith. If not, then you lied about the "one role" and it turns out that they haven't BECOME "one role".

This motte-and-bailey strategy is unproductive and disrespectful to the people you are addressing.

Re: Thoughts and feelings around Claude Design

#238
post #130

Earlier quoted context omitted.

As we know from THERAC-25, etc., comprehensively verifying that code works the way it's expected to is not actually very easy - it's perhaps one of the hardest parts of building any system more complex than a toaster.

Thankfully the CRUD app that is being developed by some random startup is not likely to cause as much harm as the THERAC.

Depends on what it's doing.

Worth noting that you've slipped from "checking whether something works is easy" to "well, it's probably not as harmful as a very notable failure if it fucks up."

The bar lowers so quickly.

Re: Thoughts and feelings around Claude Design

#239
post #181

Earlier quoted context omitted.

They're definitely not subsidizing API pricing The cost of a thing, is relative to its source costs. They are subsidizing API pricing, if you consider all the costs to provide the service, including all model creation, training, etc costs. But that doesn't mean they will be more expensive, longer term. The cost of compute will go down as time goes on. Each year it will get cheaper. Same for power requirements, comput…

If those cost of compute is going down, then eventually it will go down enough that we will run on our LLMs locally and Anthropic will go out of business.

The industry will shift, yes. At some point, remote LLM compute will be like AWS.

Everyone can do baremetal at home and run on it, or VMs, containers. Many don't.

However, you'll still want the best model and toolset. So there is some place for them to pivot to. Something for them to sell or licence.

It will be interesting to see where the all lands, a decade from now. Who will be left?

Re: Thoughts and feelings around Claude Design

#240

Earlier quoted context omitted.

lol yes. At least in agency world, a common approach in the last X years has been that designers create entire pixel-perfect, component-based sources-of-truth in Figma (which evolve! they aren't delivered static and complete) -- these are also what the client sees and approves, or at the very least they see branded deck slides that incorporate the Figma designs. Anyways, front end then re-implements from Figma into C…

Why don’t we just teach the designers code / the coders design? This feels very Programmer-Analyst split

https://youtu.be/-ahtp0sjA5U?si=iXwfIBcpJQvVX-AB
Post reply on HN