I was surprised to see an HTML5 cordova app time out on the tf300t that runs 'meh on my bionic. Am I hitting a wall at this resolution or something? The bionic's a trooper but I just assumed the TF300T was packing a heavier duty CPU.
The app itself is a single 100 by 100 canvas element rotating a simple triangular image and using some JS trig functions to move it around on top of a map that's mostly a grid made of a whole bunch of html divs constructing a grid with border settings and a repeating starfield background on the body (as I pick up more mobile / android-webview experience I now realize this was not such a hot idea). But I'm still wondering what the tf300 is choking on that the bionic (at least a year older) is managing to handle. Is it just res? I never had a performance problem with the bionic but was it that awesome for its time?
The app itself is a single 100 by 100 canvas element rotating a simple triangular image and using some JS trig functions to move it around on top of a map that's mostly a grid made of a whole bunch of html divs constructing a grid with border settings and a repeating starfield background on the body (as I pick up more mobile / android-webview experience I now realize this was not such a hot idea). But I'm still wondering what the tf300 is choking on that the bionic (at least a year older) is managing to handle. Is it just res? I never had a performance problem with the bionic but was it that awesome for its time?
