Websites have become so much more interactive, animated and exciting, and users have come to expect super smooth experiences. Frame drops upset visitors and leave them with a poor impression, but what happens if we have a process to run that takes more than 16m/s? Here's what I do...
I've constantly wrestled with the challenge of "when to do job X?" and I'm betting you have too. If we have a dynamic and interactive website or application then we need to ensure that the user doesn't get plagued with glitches during animations or scrolling. If you are writing a game it's an ongoing battle, but these days it's everywhere as even the simplest sites want to show off some cool stunts.