←back to thread

62 points grouchy | 1 comments | | HN request time: 0s | 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 #
tartoran ◴[] No.46178863[source]
Yes and this is my biggest anxiety of future software and interfaces to come. You won't remember how you got there or did what because there are n permutations of getting there or doing that, except they're vaguely similar but not exactly the same thing. I too want predictable software (including UIs) that stays the same until I want to change/upgrade it myself as a user.
replies(3): >>46180474 #>>46182051 #>>46187391 #
brandensilva ◴[] No.46182051[source]
I've heard from users they are burnt out on the UI many apps support. Buggy components everywhere across web, mobile, etc. e.g I can confirm that QuickBooks mobile app has so many bugs still in it for example and it's like 1/10th their web app.

I know personally I hit buggy forms and UI way more than I should preventing me from proceeding.

So I think there is an opportunity to instead have n permutations in natural language where the interface is consistent towards how the user inputs, it will just be up to the developers to support some UI for confirmation and structuring more complex input within chat itself. The biggest issue will be become discovery of what you can and cannot do without stationary UIs hinting at capabilities.

Anyways we are in new territory so it will be interesting how this plays out.i like to think of it as on demand UI but curious how others are toying with this paradigm.

We are testing a mostly display only interface for output where the majority of input comes in from chat and chat UI components right now just to see how this would work in practice.

replies(1): >>46183378 #
1. bccdee ◴[] No.46183378{3}[source]
The biggest issue will be that what you're describing will be 100x buggier than any currently existing application. If forms are buggy now, what makes you think that moving the buttons around non-deterministally would improve this?