#300ms

[markustenghamn]

Suppressing the 300ms click delay

Suppressing the 300ms click delay

By default, if you tap on a touchscreen it takes about 300ms before a click event fires. It’s possible to remove this delay, but it’s complicated. I investigated it.

The reason for the delay is double-tap. Once your finger releases the screen, the OS and browser cannot be sure yet if you’re done with your touch action, or if a second tap will follow, which would make the action a double tap…

View On WordPress

[bigmoolah]

#300Ms @itsstevieyall @beamup_breez @lastlookr #VM #mlcww

[henrycode-blog-blog]

Humans Can Perceive a Delay of 100+ Milliseconds

At  we're moving towards a better mobile experience. Speed is an important topic in mobile development.                                           

In general, we'd be talking caching or asset management. But here we're talking about the default 300 millisecond delay that users encounter on mobile browsers when a button is clicked.                              

The idea is that with a 300ms delay, the browser has the time to check if the user meant to double click. In general, most web apps won't need this, as it will only slow down its UI.

What you need to know: Humans can perceive a delay of 100 milliseconds. See for yourself. So, we'll need to work around the 300ms delay that happens when users click buttons on a mobile app.

Google engineers wrote a great article on how to handle this problem. A team of developers from the Financial Times Labs have written a library called fastclick that solves the issue!