Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Thoughts and feelings around Claude Design

samhenri.gold

Post reply on HN
Print view View original

81–90 of 253 posts

Re: Thoughts and feelings around Claude Design

#81

Post by telman17 »

markdown wrote: post #59
gregsadetsky wrote: post #52

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.

Many designers stuck with Photoshop sadly. Back when I did agency work it was absolutely normal to get PSDs of mockups.

Re: Thoughts and feelings around Claude Design

#82

Post by bayarearefugee »

xeromal wrote: post #62
markdown wrote: post #59

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.

I think his point was made regardless of his mistake

I wouldn't even classify it as a mistake, just a difference in experience regardless of what Adobe's intentions were.

As someone who has done front-end development for both web and mobile devices for a very long time in the pre-Figma days I was handed a lot more designs that were mocked up in Photoshop than Fireworks.

Re: Thoughts and feelings around Claude Design

#83

Post by operatingthetan »

girvo wrote: post #54
only-one1701 wrote: post #39

Earlier quoted context omitted.

I would ask this: which is the worse failure mode —- design not quite right, or users can’t access the app?

On the other hand, teaching taste is quite hard, and is what people respond to and what designers learn. Teaching programming is a bit of mostly solved problem, today anyway.

Realistically this doesn't mean all pure designers go away. Large orgs can have a small team that set the overall style guide and designs important pages, and the rest of the org just follows using AI to iterate.

Re: Thoughts and feelings around Claude Design

#84

Post by sarchertech »

gregsadetsky wrote: post #52
alkonaut wrote: post #17

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

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

It’s just one more example of people realizing that the code is the spec.

Re: Thoughts and feelings around Claude Design

#85

Post by brulard »

love2read wrote: post #22
dygd wrote: post #12

Earlier quoted context omitted.

It may look like a crappy Electron app, but Figma has a quite interesting architecture. The browser editor is developed in C++ and cross-compiled to JavaScript with emscripten. The rendering engine looks like its handling HTML, but it's actually rendering their own document format for cross-browser consistency. They have their own CRDT implementation to handle multi-user edits. [0] https://www.madebyevan.com/figma/bu…

I think my biggest question is who cares? What does having an interesting internal architecture have to do with the “its electron though” ideological attack.

It is made to perform much better than your typical electron app would. Saying electron-based == shitty is complete misunderstanding of the technology. Although i dislike Figma as much as the next guy, their app was in many ways very impressive. See Figma's cofounder old articles at https://madebyevan.com/figma/

Re: Thoughts and feelings around Claude Design

#86

Post by chatmasta »

juliusceasar wrote: post #64
markbao wrote: post #28

I don’t really buy that Claude Design will remove all the complexity around design. Vibe-coded apps using Claude look simpler because they are simpler. They’re not a gigantic product suite with extremely specific UI components tailored to each use case. The ‘simplicity’ is an illusion coming from conflating the complexity of a bicycle (a vibe coded app) with an airplane (an app like Figma). Building the same design s…

Most of the times people just want a bike or a car. Not everybody needs an airplane. This is going to hit Figma very hard.

Figma has been in trouble for a while. All the designers at my company switched to Cursor nearly a year ago. They made live mockups that don’t even need a spec to implement, because the expected behavior is already captured in the prototype. Claude Design makes it just marginally easier.

Re: Thoughts and feelings around Claude Design

#87

Post by operatingthetan »

esafak wrote: post #42
doug_durham wrote: post #40

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.

HTML and CSS, sure, but modern frontend design is way more than that; it's a jungle out there.

React, Nextjs, Vue, Nuxt, and Angular are pretty much what AI is the very best at coding in my experience. Probably because they are all meant to build essentially the same thing with different curtains.

Re: Thoughts and feelings around Claude Design

#89

Post by slopinthebag »

adriand wrote: post #77
mickdarling wrote: post #51

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.

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

Post reply on HN