3 ms·

This is a UI sin that should trigger public shame of developers. It really should be handled at the OS level for apps, or at the browser level for web sites: I

This is a UI sin that should trigger public shame of developers. It really should be handled at the OS level for apps, or at the browser level for web sites: If I click anything on the screen, it should react as if I clicked on what was there 300ms ago, maybe 400 or 500ms or longer. The fastest (typical) human reaction is around 300ms. If I'm clicking on something that appeared less than 300ms ago, then I'm NOT intending to click on it. Maybe the delay should be configurable, or maybe it learns the behavior for a particular user? An elderly person surfing the web might have a 1000ms propagation delay between deciding to click and clicking on a button or link. But my reflexes are closer to the 300ms point if not better on a good day. No matter how fast a human is, if a button is covered by an ad 100-200ms before they click, there's no way to not click on it. And that's bad UI. Even my (our?) favorite search engine, Duck Duck Go, is guilty of this: I will frequently accidentally click on the "WikiPedia summary" popup which has just replaced the actual top link that I wanted to be clicking on. Bad web duck!

aidos 10y ago
Heh. I've never thought of solving that via a delay before but it's a brilliant idea. I can't think of the site at the moment (but it was a popular well respected one) but yesterday I got caught 3 times in a row by this issue. I just kept thinking to myself "how could you have so little respect for your users?"
userbinator 10y ago
The fastest (typical) human reaction is around 300ms From what I've read it's more like 200-250ms, but hardware lag does bring the end-to-end closer to 300ms.
- SomeCallMeTim 10y ago
  A quick Google finds numbers from 250-280, with record reflexes as low as 110ms. I've done less than 180ms on a "hit the button after the light goes on" game at a science museum (hardware designed for it, so no built-in latency). 300ms is a good lower limit, though, if you take into account complex video processing and standard brain activity when browsing; when hitting a button when you're browsing, your brain isn't wound up and ready to react as quickly as possible. Getting that extra fast reaction really requires short circuiting some of the mental processing you'd normally do. I'm pretty sure I'm remembering 300ms from the cognitive science/UI classes I took in college. And don't forget the hardware lag in your own body. ;) The signal to click the button takes ~10ms to get from your brain to your fingers. When you think about things like sports where the accuracy of, say, releasing a ball when throwing it, needs to be in the 0.1ms range to hit your target, but your brain is actually giving the command 10ms before the ideal release time... Makes my brain hurt just contemplating how it works. Pro tip: Don't think about this while trying to throw a ball accurately.

aidos 10y ago

Heh. I've never thought of solving that via a delay before but it's a brilliant idea. I can't think of the site at the moment (but it was a popular well respected one) but yesterday I got caught 3 times in a row by this issue. I just kept thinking to myself "how could you have so little respect for your users?"

userbinator 10y ago

The fastest (typical) human reaction is around 300ms From what I've read it's more like 200-250ms, but hardware lag does bring the end-to-end closer to 300ms.

SomeCallMeTim 10y ago
A quick Google finds numbers from 250-280, with record reflexes as low as 110ms. I've done less than 180ms on a "hit the button after the light goes on" game at a science museum (hardware designed for it, so no built-in latency). 300ms is a good lower limit, though, if you take into account complex video processing and standard brain activity when browsing; when hitting a button when you're browsing, your brain isn't wound up and ready to react as quickly as possible. Getting that extra fast reaction really requires short circuiting some of the mental processing you'd normally do. I'm pretty sure I'm remembering 300ms from the cognitive science/UI classes I took in college. And don't forget the hardware lag in your own body. ;) The signal to click the button takes ~10ms to get from your brain to your fingers. When you think about things like sports where the accuracy of, say, releasing a ball when throwing it, needs to be in the 0.1ms range to hit your target, but your brain is actually giving the command 10ms before the ideal release time... Makes my brain hurt just contemplating how it works. Pro tip: Don't think about this while trying to throw a ball accurately.