News for hackers. Stuff that matters.
Re:You can't detect a touchscreen by crazygringo on Thursday May 09, 2013 @11:15AM (#5680836)
Related: what verb are we supposed to use now, for click/touch?

A couple months ago, I was writing a balloon-tutorial system for an app with a desktop and mobile version. The desktop version had to have commands like "click this, then click that". The mobile version, "touch this, then touch that." Often, the text was otherwise identical.

But what do we write when the user could be using either, for example on Windows 8? "Clicking" a link with your finger sounds strange -- there's nothing clicking. And "touching" something with your mouse seems equally strange, almost as if it implied moving the mouse but not clicking. "Press" works for buttons, but not menu items or links. "Activate" just seems weird. And writing out "touch/click" is just unwieldy.

What to do?

Re:You can't detect a touchscreen by bitwize on Thursday May 09, 2013 @12:21PM (#5681236)
But what do we write when the user could be using either, for example on Windows 8?

Windows 8 uses "tap" everywhere, which is infuriating for desktop users, who now know on which side Microsoft's bread is really buttered.

For the Web, usability guidelines have said since forever to avoid phrases like "click here", because you have no way of knowing how your page is being viewed now or might be viewed in the future. They were blithely ignored by designers and marketroids.

Normally, when a verb is called for, I say "hit this link" or "follow this link"; for buttons and menu items I say "say". E.g., "Enter your IP address, netmask, and gateway and then say OK."

Re:You can't detect a touchscreen by rlu on Thursday May 09, 2013 @12:31PM (#5681314)
I was actually going to reply to the parent and say that Windows 8 often times tells me to "click or tap". Can you give an example of somewhere in Windows 8 where it says to only tap?
Re:You can't detect a touchscreen by mbrubeck on Thursday May 09, 2013 @02:23PM (#5682101)
Of course, a large portion of laptop users have actually been tapping on trackpads to "click" for a long time now...
Re:You can't detect a touchscreen by JoshTriplett on Thursday May 09, 2013 @12:14PM (#5681181)
No matter what interface the user uses, they still "follow" links, and "press" buttons.
Re:You can't detect a touchscreen by dan1234 on Thursday May 09, 2013 @11:30AM (#5680934)
I tend to say "tap" instead of "touch" and, at a pinch, this could work for mouse users.

Saying that, most people will know what "click here" means, regardless of the input type, so I wouldn't lose sleep over it.

Re:You can't detect a touchscreen by thaumasiotes on Thursday May 09, 2013 @11:24AM (#5680901)
I would use "click". In fact, I do use "click" to refer to using touchscreens, all the time.
Re:You can't detect a touchscreen by stucox on Thursday May 09, 2013 @11:34AM (#5680966)
... which, incidentally, is the DOM event you can guarantee will be fired, regardless of the input device (unless you choose to `preventDefault()` before it gets a chance).
Re:You can't detect a touchscreen by romey on Thursday May 09, 2013 @02:28PM (#5682129)
How about

Links => "follow"

[Nested] Menus => "navigate to"

Buttons => "press"

Other => "select"

Re:You can't detect a touchscreen by tomgallard on Thursday May 09, 2013 @11:28AM (#5680923)
How about 'press' ?
Re:You can't detect a touchscreen by msgilligan on Thursday May 09, 2013 @12:22PM (#5681245)
In addition to the suggestions of others, there is 'choose' which will work in some contexts (e.g. Menus)