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

Why AI Sucks at Front End

nerdy.dev

Post reply on HN
Print view View original

131–140 of 183 posts

Re: Why AI Sucks at Front End

#131

Post by danlugo92 »

meisterfeister wrote: post #50
khasan222 wrote: post #36

Ngl I’m reading this article after having used ai to build a beautiful front end that is pixel perfect. Yes ai can’t see, it only understands numbers. So tell it to use image magick to compare the screenshot to the actual mockup, tell it to get less than 5% difference and don’t use more than 20% blur. Thank me later. I built a whole website in like 2 days with this technique. Everyone seems to have trouble telling ai…

Yes can you share the front end that you created using this technique?

Imagine being a luddite in the big 26

Re: Why AI Sucks at Front End

#133

Post by cendyne »

apwheele wrote: post #125
khasan222 wrote: post #36

Ngl I’m reading this article after having used ai to build a beautiful front end that is pixel perfect. Yes ai can’t see, it only understands numbers. So tell it to use image magick to compare the screenshot to the actual mockup, tell it to get less than 5% difference and don’t use more than 20% blur. Thank me later. I built a whole website in like 2 days with this technique. Everyone seems to have trouble telling ai…

I am a backend guy, so forgive my ignorance, but for web based apps I am confused what "pixel perfect" even means. I can build a site to look one way on my computer, it will most likely not look the same way on whatever device you use to access the site. Feeding the model images for my local computer sounds like a recipe given my experience with the tools to have it over-optimize for the wrong end device.

"Pixel perfect" is about attention to detail and consistency. Margins, padding, or the combination of these inside other containers will stick out when they're not consistent.

Here's an example that I personally encountered: what if you have a Text and it has a certain left margin. Then another heading except it has a nested button component (which internally comes with some padding). Then the "Text" in both aren't aligned from section to section and it is jarring.

Re: Why AI Sucks at Front End

#134

Post by thejazzman »

jeixjejdjwjx wrote: post #92
thejazzman wrote: post #86

Earlier quoted context omitted.

https://poolometer.com I built this frontend with Sonnet 4.5 last Fall and I’m about to “launch” it I used only prompts, but those prompts included ChatGPT’s research on Memphis design ;) Using codex for front end design is like asking the valedictorian mega nerd to paint your portrait. Gemini and Claude are both artists.

Sorry to be the one to break it to you, but no, you did not design a website just fine with AI. It’s not even just “good”. It’s average. Painfully average, to the point of it being easily mistaken for a scam. Very bad results—as expected from an AI. Nothing to brag about here.

I can't help but think you and the other commenters reducing this to slop didn't even try the product. I thought it went without saying that I wasn't posting to show a marketing landing page.

Re: Why AI Sucks at Front End

#135

Post by thejazzman »

FiberBundle wrote: post #127
thejazzman wrote: post #86

Earlier quoted context omitted.

https://poolometer.com I built this frontend with Sonnet 4.5 last Fall and I’m about to “launch” it I used only prompts, but those prompts included ChatGPT’s research on Memphis design ;) Using codex for front end design is like asking the valedictorian mega nerd to paint your portrait. Gemini and Claude are both artists.

Looks as if AI sucks at frontend tbh.

Is this a critique of the marketing page or of the product?

Re: Why AI Sucks at Front End

#136

Post by thejazzman »

camillomiller wrote: post #95
thejazzman wrote: post #86

Earlier quoted context omitted.

https://poolometer.com I built this frontend with Sonnet 4.5 last Fall and I’m about to “launch” it I used only prompts, but those prompts included ChatGPT’s research on Memphis design ;) Using codex for front end design is like asking the valedictorian mega nerd to paint your portrait. Gemini and Claude are both artists.

Well it works but it also looks like every other generic bootstrap based website with not even an original palette choice. Great for a project like this, unusable for any client work

Is this a critique of the marketing page or of the product itself?

I didn't intend for this to be about the marketing page -- what you say is true of just about every marketing page. They're prevalent because they are good at distilling information without overwhelming the user. But I agree I can do better and will work on this more, I really appreciate getting this feedback

Most people look at pool chemistry/maintenance as painfully overwhelming, so for everyone to say this looks boring or mundane is a bit validating. No one has (yet!) said they don't understand the product, it's purpose, or it's value :)

Re: Why AI Sucks at Front End

#138

Post by thejazzman »

NewsaHackO wrote: post #117
jeixjejdjwjx wrote: post #92

Earlier quoted context omitted.

Sorry to be the one to break it to you, but no, you did not design a website just fine with AI. It’s not even just “good”. It’s average. Painfully average, to the point of it being easily mistaken for a scam. Very bad results—as expected from an AI. Nothing to brag about here.

I completely disagree. Making a average website is the goal of most businesses that are selling an actual product. His website looks modern and welcoming and does not distract or take away from the actual content. This exactly what most people should aim for. Some actual constructive criticism is some o the icons in the example log mood look weird on my phone, with really small emojis overlapping the face emoji

Thank you, agreed, I will iterate on this more.

When I shared this I wasn't thinking about the marketing site -- I meant to show the product itself. Given the feedback here I no longer think it's a good representative as-is, especially with the generic SVGs / rounded cards

Re: Why AI Sucks at Front End

#139

Post by thejazzman »

pants2 wrote: post #89
thejazzman wrote: post #86

Earlier quoted context omitted.

https://poolometer.com I built this frontend with Sonnet 4.5 last Fall and I’m about to “launch” it I used only prompts, but those prompts included ChatGPT’s research on Memphis design ;) Using codex for front end design is like asking the valedictorian mega nerd to paint your portrait. Gemini and Claude are both artists.

Sorry but this website screams AI slop to me. Very sparse, lots of cards and random icons and rounded corners, looks like a few messages in to a Claude code session

I intended to share the product rather than the marketing page. I mean, I didn't intend to share this at all yet because it's not done, but when I saw people asking for examples..

But yeah, marketing site looks like a marketing site. I'm realizing now that a lot of my app's internal design/flair is missing from the marketing page -- so I appreciate your looking/commenting

Re: Why AI Sucks at Front End

#140

Post by squidbeak »

the_gipsy wrote: post #118
squidbeak wrote: post #112

Earlier quoted context omitted.

If AI is being used to lower salary burdens, it categorically is partially or wholly replacing developers. Meanwhile, elsewhere in this discussion, you can read examples of people who have used AI entirely to build their product. Previously they'd have had to hire a developer or become one themselves. This suggests to me it is indeed replacing developers - just not where you are choosing to look.

No, it's the economy that is shifting and the reason developers are getting fired. This causes wage lowering. AI is the excuse that let's companies corporate-speak around the economy.

Work lost by freelancers and contractors to AI can't be brushed out of sight with a 'No' and an unrelated vague assertion that the economy is shifting.
Post reply on HN