>Since this submission has been on the front page of HN for hours now, clearly people like it as it is. I don't think I need to change anything about it.
That's not really how it works. People like it in spite of the bad vibe coded UI. That doesn't mean that the UI is good. The criticism was clearly correct. I don't feel bad about publicly criticizing the UI to your face, either, because it's not like you were the one who designed/created it anyway--by the same reasoning, I don't see any reason to get defensive about it, since you have not invested very much of yourself into it either.
This has become a bit of a pet peeve of mine in general. Over the last six months or so I've been inundated with all kinds of lazy, bad vibe-coded UIs via my normal internet usage. It feels paradoxical in a way, because AI tooling should make it easier than ever to fix obvious problems, and yet UIs have gotten worse.
I have two theories for why this is: (1) usage of AI tooling conditions people into engaging with their creations in a certain hands-off, uninvolved, low-attention surface level way; or perhaps (2) those who care about their UIs were the people who were already creating UIs pre-AI, and so the marginal effect of AI tooling has been to increase UI creation amongst precisely the population who cares the least about what they are putting out.
I've also been developing a very strong personal revulsion towards the Claude default design language, including and especially the gold-on-black color scheme, although I admit that this is entirely by association and not because of its inherent qualities per se.
In this particular case it used to not have any text at the top. Just click a model, chat.
I decided that that wasn't very user friendly. It doesn't tell people what it is. Or how to use it. It doesn't explain any of the concepts or vocabulary.
So I asked it to add those things, above the main interface, including the steps people need to take to use it. I think it did great, and I think the small text sizes with a clear title let people who need it, read it, and people who don't can just scroll down. Even with the text it's 600 words.
I like the effect of what it's done. It's better than I would have done if I had written those intro words myself.
Clearly it resonates with people, this thing has been on the front page of HN for 4 hours and with 110 points is by far the most popular thing I've ever posted here.
It isn’t about how small the text is or how easy it is to skip. Humans are not transformers with multiheaded anttention. Human brains do not process one million tokens in parallel. Humans have caloric constraints and will be annoyed if you ask them to process irrelevant information.
Therefore, when showing something to humans, the first thing they see should be the first thing you want them to see. And since this is a demo, the first thing they see should be the demo, with sane defaults, above the fold.
Also, it is likely that no one (including the author) has read this “fine print” because it includes incorrect information. GPT-4 isn’t a frontier model anymore.
It's clear that this was vibecoded. I'm antivibecoding, but here's a tip.
Don't focus on the actual code or the actual UI. You need to give your model a way to see its output. If it just pumps code, it looks at the code. If you let it look at the rendered UI, whether by manually taking screenshots, or making it so that the agent looks at the browser output automagically (with a webdriver or selenium or puppeteer or a skill or whatever), it will fix whatever issues it sees on itself, and it will never be content with delivering something that looks as bad as this.