Live data from Hacker News

Thoughts and feelings around Claude Design

samhenri.gold

211–220 of 253 posts

Re: Thoughts and feelings around Claude Design

#211

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.

It’s not the designers pushing that, it’s the product managers and marketers. UXDs generally roll their eyes at pure branding stuff.

Guess it’s a bit of both.

Whenever I said “this is a website, not an app” I would get confused looks from designers.

UX people fight some of the BS, but “looking pretty” usually wins over “being useful”.

Re: Thoughts and feelings around Claude Design

#212

Earlier quoted context omitted.

Homogenous might be awesome. I miss predictable UIs.

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

We can have both distinctive designs and predictable UX. In fact, we did, for several decades!

Re: Thoughts and feelings around Claude Design

#213

Earlier quoted context omitted.

Homogenous might be awesome. I miss predictable UIs.

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.

Re: Thoughts and feelings around Claude Design

#214

Earlier quoted context omitted.

Homogenous might be awesome. I miss predictable UIs.

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

If "everything looks the same" means no more branding obsession, sign me up.

Re: Thoughts and feelings around Claude Design

#215

Earlier quoted context omitted.

[flagged]

> Also, you certainly got some brass, linking an entirely AI generated article in a forum where extreme distaste is registered for entirely AI generated posts. > How is your comment not downvoted to oblivion? I'm sure there's a polite way to say things. I heavily dislike LLM content, but if you read the content, it's actually got information of value.

> I'm sure there's a polite way to say things.

That was the polite way of saying things. The phrase "if you couldn't be bothered to write it why would anyone bother to read it" was a saying from usenet times.

The truth is it took the author less time to "write" that piece than you to read it. It's a blog. There's no deadline, and yet they couldn't take the time to actually type out their own thoughts.

> I heavily dislike LLM content, but if you read the content, it's actually got information of value.

If it was so valuable the author would have written it themselves.

Re: Thoughts and feelings around Claude Design

#216
post #141

This design tool space died a long time ago for me when InVision shut down and pivoted to a digital whiteboard. It’s a really difficult space. But the fundamental problem is that it’s hard to get a design system right long-term, especially because it’s so intertwined with your code and whatever component library you use, which is a layer your designer will never touch. I don’t really see Claude Design fixing the fund…

The solution is an open, flexible, scriptable and drawable canvas where design and code co-exist in exact harmony. Design changes directly modify front-end code, and front-end code directly modifies design equivalently. I see the endgame as a model where designers and FEE's are co-owners and co-authors of the front-end with zero handoff.

Microsoft Frontpage

Re: Thoughts and feelings around Claude Design

#217
post #31

Earlier quoted context omitted.

I've been a developer for over 2 decades and I've been using AI in our react codebase for the past 3 months. Outside of some optimizations there's not much a designer couldn't debug through Claude Code. 90% of the industry is toast. I want to be wrong because I'm watching the death of my entire career, but everything I've seen is pointing to this as an inevitability. We are shipping better and more secure code, and d…

I've been writing code for 50 years and it looks now that we have seen sunrise and are about to see sunset on humans writing code by hand. Is that bad? Not to anyone who has managed dev teams and is familiar with the incredibly tortuous and painful business of trying to corral a bunch of humans with varying skill and enthusiasm levels to create software. We have tied ourselves in knots with things like Agile just try…

We're moving so fast that management can't keep up on reading what's happening, they're going to slow development down by cutting the massive cost of employing people. There just aren't enough features to justify the breakneck pace.

It's a golden era for business, but the industry will employ many fewer people.

Re: Thoughts and feelings around Claude Design

#218

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-colla…

Watching the hive mind of the industry go almost overnight from inVision to Figma shows there's just no mote in this segment... people can leave just as quickly as they came, have no loyalty, and are all about fashion and vibes.

Re: Thoughts and feelings around Claude Design

#219
post #33
post #30

Earlier quoted context omitted.

It's very easy to know when code is wrong: it doesn't work the way it's expected to. So you explain to the AI what's wrong and the AI fixes it.

Your designers are going to be looking at the layout; they're not going to notice if it's slow, uses too much memory, is not maintainable, doesn't follow repo patterns, etc. Do you think it is reasonable to expect a person with an arts degree to know this?

"This works but the app is slow, can you optimize it." I'm not even kidding, most of the time this is all that's needed. Repo patterns don't really matter because humans barely end up looking at the code.

We've had a customer send us a prototype of what they wanted built with AI, and they don't have a college degree in anything. It followed our codebase patterns without any prompting, included tests, and all we had to do was wire up the backend.

Re: Thoughts and feelings around Claude Design

#220

Earlier quoted context omitted.

Homogenous might be awesome. I miss predictable UIs.

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

Agreed. I miss the quirky UXes of the past. Kai Power Tools was one great example.
Post reply on HN