Live data from Hacker News

Thoughts and feelings around Claude Design

samhenri.gold

91–100 of 253 posts

Re: Thoughts and feelings around Claude Design

#91
post #88

Can someone please help me understand why people are obssessing over this as a Figma killer and not, more clearly, a shot at Replit, Lovable, etc.?

The AI app builders are part of the AI economy already. They are essentially re-selling tokens/compute. It's an existing horse race.

Bringing a Figma killer to the market is converting a conventional software sector into an AI one. So it's more disruptive.

Re: Thoughts and feelings around Claude Design

#92

I used it today to take a look at my previously built design system with Logos, branding, fonts, and everything else. After a lot of annoying tweaking back and forth, finally, I got something that was satisfactory. Then I looked at the usage and it said I had used 95% of my Claude design usage for the week! This isn't a real tool. This is a plaything, if that's what they're providing as examples.

It's in research preview. I suspect limits are low on purpose. FWIW, I gave it twelve screenshots of different pages in my app and it did a really excellent job fixing them up. Consumed just 40% of weekly quota - still too high but it's probably a YMMV situation.

Re: Thoughts and feelings around Claude Design

#93
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…

This is so context-dependent. Coding some generic crud app is indeed becoming more automated, but most of the stuff I end up building is just way outside the capabilities of current LLMs to accomplish without significant steering and gasps hand written code. Most of the stuff LLMs are good at ones hotting are the same things a non-coder could build with no-code platforms anyways. Which is great imo, it means we can utilise our skills and expertise on stuff that is more "cutting edge".

Re: Thoughts and feelings around Claude Design

#94
post #77

Earlier quoted context omitted.

I had a similar experience with running out of usage quite quickly, after setting up one design system properly, and then getting pretty close with a second one. But it's a research preview - I'm sure it will change. I was quite happy with what I pulled off using the first design system: I wanted a new footer section for my IPAAS startup, it generated four options, the fourth of which was quite good. We iterated on i…

I mean, it's fine and serves it's purpose, but I'm a bit confused what you are getting that you wouldn't get with the millions of pre-made designs and design systems? Like Tailwind UI for example. https://tailwindcss.com/plus/ui-blocks

Iterative experience (experimenting with different ideas, deciding what works best) and speed of execution (once I was happy with it, making it happen required almost no work).

Re: Thoughts and feelings around Claude Design

#95

Earlier quoted context omitted.

@kevinsync's answer is 100% correct and it's been this way for the last ~~~20? years? at least - only it was "Photoshop files hold the (design) truth" before - now it's figma. But yes, the "design to code" gap has always been where designers' intentions were butchered and/or where frontend developers would discover/have to deal with designs that didn't take into account that some strings need more space, or what to d…

> 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.

I was in web agencies since like 2002-2015, always got PSDs from either clients or internal designers

Re: Thoughts and feelings around Claude Design

#96
post #79

Earlier quoted context omitted.

In my opinion this should have always been the case. All designers should be able to code and do html/css. It's the medium of design.

> All designers should be able to code and do html/css. It's the medium of design. So a fashion designer can mass produce clothing? So an interior designer can build a house? This designer should has never held.

The analogies you have offered aren't great.

For example designers and developers both use the computer as their primary medium of working. Their outputs resemble each other very closely, despite having a different underlying form.

Contrast that to the interior designer building a house, well those are different mediums. There is no efficiency gain from the interior designer designing the plan and also implementing it. Where as with a designer working in code there is one.

Fashion designers do indeed make clothing by hand, it's a very important part of their craft. This example disproves your stance.

Re: Thoughts and feelings around Claude Design

#97
post #3

Excellent post. I share the author's sentiment which is essentially "to hell with Figma, at least fix Sketch". Been feeling very lonely in may hatred towards Figma, which is for a whole bunch of reasons (among others, it's an incredibly shitty, memory and CPU hungry Electron app that looks and feels worse than any more or less well designed web site), but now after reading this I realize the number of reasons has dou…

(author of the post here) I cut a paragraph how Figma costs cuckoo bananas money for your entire team for the privilege of enduring this byzantine nightmare. And they paywall certain features, which you likely can't get authorization for, so you have to do more hacks on top of hacks on top of the “gold standard” practices I shared in the blog post. The price ramp is not gradual.

I think this is what kills them, not AI. I know 2 companies (enterprise level) who are migrating away from Atlassian atm just gets too costly.

Re: Thoughts and feelings around Claude Design

#98
post #77

Earlier quoted context omitted.

I had a similar experience with running out of usage quite quickly, after setting up one design system properly, and then getting pretty close with a second one. But it's a research preview - I'm sure it will change. I was quite happy with what I pulled off using the first design system: I wanted a new footer section for my IPAAS startup, it generated four options, the fourth of which was quite good. We iterated on i…

I mean, it's fine and serves it's purpose, but I'm a bit confused what you are getting that you wouldn't get with the millions of pre-made designs and design systems? Like Tailwind UI for example. https://tailwindcss.com/plus/ui-blocks

I find that with the ubiquity of Tailwind, developers treat design as a "solved problem". What's missing is the specific evolution of one's product and the resultant information architecture. The sibling response is my experience as well, design is an incredibly interactive exercise.

Granted, not every component on every surface will need this amount of scrutiny. But I'm usually the outlier developer warning teammates that design is not a solved problem. Granted, there's a huge difference between an existing app and its evolution and throwing a nextjs landing page up in search of any life.

Re: Thoughts and feelings around Claude Design

#99
post #94

Earlier quoted context omitted.

I mean, it's fine and serves it's purpose, but I'm a bit confused what you are getting that you wouldn't get with the millions of pre-made designs and design systems? Like Tailwind UI for example. https://tailwindcss.com/plus/ui-blocks

Iterative experience (experimenting with different ideas, deciding what works best) and speed of execution (once I was happy with it, making it happen required almost no work).

Thats fair. Could you have the same iterative experience with an LLM, but starting with a prebuilt base and iterating from there?

Re: Thoughts and feelings around Claude Design

#100
post #79

Earlier quoted context omitted.

In my opinion this should have always been the case. All designers should be able to code and do html/css. It's the medium of design.

> All designers should be able to code and do html/css. It's the medium of design. So a fashion designer can mass produce clothing? So an interior designer can build a house? This designer should has never held.

Fashion designers can, in general, work with fabric, yes. And an interior designer should probably have some idea of how to paint at the very least. To me with web design so much of what matters is encoded in the CSS and HTML that it is the final design product. Anything produced before is a sketch, a concept, but it's not a design.
Post reply on HN