3 ms·
The thing about a mouse interface is that it's a lowest-common-denominator approach for a lot of things that works pretty ok. Certainly better for that than the
by ska 6y ago
The thing about a mouse interface is that it's a lowest-common-denominator approach for a lot of things that works pretty ok. Certainly better for that than the text-only interfaces it's largely replaces. This is also why the web is so married to it, 'cause you can navigate around a bunch of semi-consistent information.
The average confused user will probably do better randomly mousing around than trying to juggle keys, or even worse "visually" navigate using arrow keys or something.
But if the interface is powerful and the user is skilled (both significant "ifs") then important operation can be done before your hand would reach the mouse, let alone do anything with it.
I suspect the most efficient is a mix of both, mice are pretty good at selecting from a long list of options, for example.
A lot of IDEs these days contain pretty underpowered editors and slow you down by relying on the mouse too much. If that's all you've tried, you may not have any idea why keyboard interfaces can be a lot more efficient for some tasks....
- thanato0s 6y agoI agree with most of what you're saying. Now, about the skills of the users, I think people are smart and can learn more easily than we think, if and only if they're taught right. It's what I tried to do. I don't know if I succeeded, but so far I had only positive return, so it's encouraging :) About the mix of both: I agree if I'm a long period on my keyboard or on my mouse, but not interleaving the use of both.
- ska 6y agoThe point about skill is that an unskilled/inexperienced user is typically going to have more trouble navigating a keyboard based interface than a mouse based one - nothing about how easy or hard it is to gain that skill. Agree context switching between both too much is a pain.