←back to thread

62 points grouchy | 1 comments | | HN request time: 0.001s | source
Show context
bccdee ◴[] No.46178688[source]
> Users get personalized interfaces without custom code.

Personalized interfaces are bad. I don't want to configure anything, and I don't want anything automatically configured on my behalf. I want it to just work; that kind of design takes effort & there's no way around it.

Your UI should be clear and predictable. A chatbot should not be moving around the buttons. If I'm going to compare notes with my friend on how to use your software, all the buttons need to be in the same place. People hate UI redesigns for a reason: Once they've learned how to use your software, they don't want to re-learn. A product that constantly redesigns itself at the whims of an inscrutable chatbot which thinks it knows what you want is the worst of all possible products.

ALSO: Egregiously written article. I assume it's made by an LLM.

replies(8): >>46178863 #>>46179118 #>>46179820 #>>46180211 #>>46180547 #>>46181428 #>>46181458 #>>46183968 #
michaelbuckbee ◴[] No.46181458[source]
Consider Google's search results page (setting aside the ads and dark patterns for a moment) as a form of generative UI.

You enter a term, and depending on what you entered, you get a very different UI.

"best sled for toddler" -> search modifiers (wood, under $20, toboggan, etc.), search options, pictures of sleds for sale from different retailers, related products, and reviews.

"what's a toboggan" -> AI overview, Wikipedia summary, People Also Ask section, and a block of short videos on toboggans.

"directions to mt. trashmore" -> customized map of my current location to Mt. Trashmore (my local sledding hill)

Google has spent an immense amount of time and effort identifying the underlying intent behind all kinds of different searches and shows very different "UI" for each in a way makes a very fluid kind of sense to users.

replies(2): >>46184072 #>>46187259 #
1. grouchy ◴[] No.46184072[source]
I totally agree with this, and I'd go even further.

When I'm having trouble with software, I often turn to Google to figure out how to use it. I'm then directed to a YouTube video, help article, or blog post with instructions.

My take is that people are already accustomed to this question-and-answer model. They're just not used to finding it within the application itself.