Comment by joenot443
4 hours ago
A touchscreen is a way more natural and intuitive interface than a mouse cursor driven by a trackpad.
If I'd never used a laptop before I'd probably do the exact same thing as the kids!
4 hours ago
A touchscreen is a way more natural and intuitive interface than a mouse cursor driven by a trackpad.
If I'd never used a laptop before I'd probably do the exact same thing as the kids!
Exactly. Why on Earth would they default to touching something away from the screen that's an imperfect map to it when they can just touch the thing they want directly? I've seen so many people saying they don't understand and would never use a touchscreen on a laptop, and I just have to think they've not really been around non-technical adults or children.
Because the ergonomics are shit. Holding your arm up is tiring.
For interacting with a UX that's designed around keyboard and mouse? I get how it's intuitive to reach out and touch something you can see, but in terms of much of the UX it doesn't make any sense.
You lose control without a desktop and mouse. I can't even begin to count the number of times I got hit with a dark pattern where an app steers me in a direction that I can't click out of because on touch interfaces, you have less control.
" you have less control."
Keyboard and mouse don't give you any more autonomy over the application developers state machine.
I'm not sure I understand the claim of "being in control". The UX is different, sure, often. But that's not "control" over the design of the application.
I feel so constricted and frustrated when I have to use my phone. I often even put things off until I can get back to my computer.
On a touchscreen, I can tap. That's it. Select? Tap. Move? Tap. Highlight? Tap. The only one that makes sense is draging for moving, but even that's a pain in the butt because it often misinterprets the tap+hold duration that's necessary before it works. When I'm editing text (navigating, cut-n-paste, etc.), it gets what I want wrong more often than it gets it right, I mean like 80/20.
With the phone, they had a green field to design an entirely new UX for touch interfaces, so there's no legacy to blame.
Sure they do, with KB/M against a browser app you can open the dev console, you can inspect element, you can do all sorts of things that you can't do in a native app for touchscreen only.
2 replies →