upvote

points

by joenot4434 hours ago |
comments
upvoteby MrMetlHed4 hours ago|
next
[-]
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.
reply
upvoteby ahartmetz1 hours ago|
parent|
[-]
Because the ergonomics are shit. Holding your arm up is tiring.
reply
upvoteby ghusto3 hours ago|
prev|
next
[-]
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.
reply
upvoteby saturn86014 hours ago|
prev|
[-]
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.
reply
upvoteby fsloth4 hours ago|
parent|
[-]
" 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.

reply
upvoteby ghusto3 hours ago|
parent|
next
[-]
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.

reply
upvoteby mplewis3 hours ago|
parent|
prev|
[-]
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.
reply
upvoteby saturn86013 hours ago|
parent|
next
[-]
Exactly. I was planning to write these reasons but I refrained because the use cases are endless. It boils down to the fact that you can more easily escape the current context for something else.
reply
upvoteby fsloth1 hours ago|
parent|
prev|
[-]
Browser developers implemented the dev console there. You are not reaching it ”just because you have kb/m”. You can reach dev tools as easily via touch on a pc with touch support.
reply