Checked on Chrome,
Checked on CocoonJS compilation
it's especially visible with bigger objects (like 1/2 screen etc)
(even with not many collision checks (below 200)
Probably missed v-syncs. The logic behind the movement should mean it moves perfectly smooth, providing the screen refreshes match up exactly to redraws.
paradoxally it works better on my CocoonJS compilations than on Chrome (32.0.1700.107)
anyway: can I do anything?
in case of mobile my app is 1280x720, but I tested it on 854x480 phone (2x core)
Develop games in your browser. Powerful, performant & highly capable.
Probably not, hopefully future versions of Chrome will have more accurate rendering with better performance! Google's stated goal for 2014 is to get 60 FPS smooth rendering in mobile Chrome.