I'm a designer, but I admit it's really hard to predict what products and UX are going to work in the AI age.
Chatbots have been tried for a decade and were a total failure. With AI, it has become the fastest-growing way to interact with technology, ever.
GPT-5 tried to have an auto router and create abstraction for the user; people hated it. Instinct and Muse are doing the same with a different framing; it's going wild.
There are tons of these little examples where a small difference in framing, a small threshold in tech, and product assumptions completely flip on their heads.
It's amazing to follow but requires you to be way more flexible in your assumptions.
GPT-5's auto routing was bad, you'd get off the cuff bad answers for hard questions and overthinking on the banal. Also, with a chatbot the idea is that it's a back and forth but 5 minutes of thinking kills that, whereas fire and forget is core to the idea of autonomous agents.
Agents are going to replace almost all the UI in computers. For a trivial example, things like a control panel or settings menu will cease to exist, you'll handle coarse things via conversation ("set volume to 20%"), and UIs will be presented only for things where chat is cumbersome ("the password for the printer is !-*Donkey_Loves_Shrek^^@"). The UI that remains will become heavily decoupled, like supercharged versions of the office ribbons, with the intent that the agent will compose menu fragments and capability widgets dynamically so you only ever need to see controls for the settings that are relevant and that you care about.
Sorry for being dismissive. What I mean is, volume is something people generally don’t think about in percentages, but by feel/ear. It’s also adjusted so often and impulsively that doing it via chat would be extremely slow and unergonomic. So yeah, I don’t think that should happen.
Not saying you won't be able to invoke the volume control widget on a screen, but when harnesses are always listening, models are lower latency and you're interacting with a device from the other side of the room in a lot of cases (even PCs, via 72" wall mounted monitors), it'll be a lot more ergonomic.
There was a study that showed users "felt" faster on a keyboard even while completing tasks faster on a mouse. Similarly, with low latency models, "chromium volume 20%, actually, 10%" will be faster than clicking the sound control icon, finding the chromium volume from the list and reducing it, not to mention you don't have to look away from what you're doing. Direct interaction will probably only be faster if you need extremely precise control, for example, you wouldn't do digital painting with an agent, which seems pretty intuitive.
I mean maybe I‘m an outlier but I always use the physical buttons or knobs to control volume on my devices. I think that is by far the fastest, most exact and overall most user friendly and unobtrusive option, even when you have an agent that‘s always listening (which is a future I don‘t want). The point about being across the room is fair.
About that study: I‘m interested to read it, as it seems to contradict established literature on UX (not to mention lived experience) - do you have a link for that?
Tognazzini, Maximizing Human Performance; Omanson et al. 2010, Comparison of Mouse and Keyboard Efficiency; Card, Moran & Newell 1980, Keystroke-Level Model.
I seemed to recall that Tog made that point back then. Note that both Tog‘s text and Keystroke-Level are from the very early days of GUIs, so, grain of salt.
Omanson, OTOH actually contradicts them a bit: expert users are generally faster with well-learned shortcuts – a widely-held view point and the whole reason for shortcuts.
Essentially. I don't know much Linux, but I've had no problems putting together a capable, well-configured, and secure Linux box by using Claude Code as the CLI 99% of the time. Occasionally it gives me a command that needs to be pasted into a separate terminal window, but for the most part it just works on its own (and boy, does it struggle sometimes.)
A key point is that the box might as well be running BeOS or Windows or HP-UX or OS/360 or something. It doesn't matter much anymore, any more than my choice of programming language does. Requires some mental adjustment.
Adrig · · focus · HN ↗
Chatbots have been tried for a decade and were a total failure. With AI, it has become the fastest-growing way to interact with technology, ever.
GPT-5 tried to have an auto router and create abstraction for the user; people hated it. Instinct and Muse are doing the same with a different framing; it's going wild.
There are tons of these little examples where a small difference in framing, a small threshold in tech, and product assumptions completely flip on their heads.
It's amazing to follow but requires you to be way more flexible in your assumptions.
CuriouslyC · · focus · HN ↗
Agents are going to replace almost all the UI in computers. For a trivial example, things like a control panel or settings menu will cease to exist, you'll handle coarse things via conversation ("set volume to 20%"), and UIs will be presented only for things where chat is cumbersome ("the password for the printer is !-*Donkey_Loves_Shrek^^@"). The UI that remains will become heavily decoupled, like supercharged versions of the office ribbons, with the intent that the agent will compose menu fragments and capability widgets dynamically so you only ever need to see controls for the settings that are relevant and that you care about.
ch_sm · · focus · HN ↗
haha oh god no please don’t.
EDIT:
Sorry for being dismissive. What I mean is, volume is something people generally don’t think about in percentages, but by feel/ear. It’s also adjusted so often and impulsively that doing it via chat would be extremely slow and unergonomic. So yeah, I don’t think that should happen.
CuriouslyC · · focus · HN ↗
There was a study that showed users "felt" faster on a keyboard even while completing tasks faster on a mouse. Similarly, with low latency models, "chromium volume 20%, actually, 10%" will be faster than clicking the sound control icon, finding the chromium volume from the list and reducing it, not to mention you don't have to look away from what you're doing. Direct interaction will probably only be faster if you need extremely precise control, for example, you wouldn't do digital painting with an agent, which seems pretty intuitive.
ch_sm · · focus · HN ↗
About that study: I‘m interested to read it, as it seems to contradict established literature on UX (not to mention lived experience) - do you have a link for that?
tty2 · · focus · HN ↗
[dead]
CuriouslyC · · focus · HN ↗
ch_sm · · focus · HN ↗
I seemed to recall that Tog made that point back then. Note that both Tog‘s text and Keystroke-Level are from the very early days of GUIs, so, grain of salt.
Omanson, OTOH actually contradicts them a bit: expert users are generally faster with well-learned shortcuts – a widely-held view point and the whole reason for shortcuts.
CamperBob2 · · focus · HN ↗
ch_sm · · focus · HN ↗
CamperBob2 · · focus · HN ↗
A key point is that the box might as well be running BeOS or Windows or HP-UX or OS/360 or something. It doesn't matter much anymore, any more than my choice of programming language does. Requires some mental adjustment.
ch_sm · · focus · HN ↗
> don't know much Linux, but I've had no problems putting together a capable, well-configured, and secure Linux box by using Claude Code
How can you be sure of it being well configured and secure? Especially if you don‘t know much about Linux?
CamperBob2 · · focus · HN ↗
In practice, that means I at least stick around and watch when Claude tells me to curl | sudo bash something. :-P
mech422 · · focus · HN ↗
tty2 · · focus · HN ↗
[dead]