3 ms·

Thanks for testing! Which device are you using? That should not be "terribly janky" in general. It's pretty smooth on my testing devices (nexus 4, nexus 5 and s

Thanks for testing! Which device are you using? That should not be "terribly janky" in general. It's pretty smooth on my testing devices (nexus 4, nexus 5 and sony z3c). The second part of your comment makes close to no sense. There are a lot optimizations done in a web rendering engine, both on the css/layout/painting part and in the js engine. A modern web engine goes to the GPU as much as possible, and is very comparable to what a "native" toolkit does (I'm not convinced that android's xml layout/views are really more native than html/css).

bluehex 11y ago
I am on Nexus 5 and had a similar experience as OP when trying the home screen replacement. A bunch of the home-screen icons were missing and when I clicked on them they opened a completely different App that wasn't even on the screen. Trying to click on rows in the settings App did nothing, or hung, before finally responding. I'm not sure if a jank is the right word (it wasn't in the scrolling performance sense) but it felt quite buggy and unresponsive.
striking 11y ago
OnePlus One, although I'll remark that it was a long time ago.