[rogerbinns]

Chrome on Linux (with 16GB RAM) - works fine.

Chrome on Android 4.0 (Galaxy Tab): Takes about 30 seconds and then I just get some text and a picture of the car. Chose 'Request Desktop Site' and it is fairly close to desktop experience. Sometimes you get bits of white page as it brings the images in.

Builtin browser on Android 4.1 (not Chrome): I had to request desktop site again. Almost usable. There are always images displayed, but drawing after using your finger may take a second or two.

Safari iPod Touch 4G iOS 5.1 - sporadically somewhat usable for one touch interaction.

[se85]

Thats fascinating that Chrome on Android is capable of delivering the desktop experience of this concept even with the limited hardware specs of the Galaxy Tab.

I wonder whats so different under the hood of Safari Mobile on iOS 5 vs Chrome on Android 4 to deliver such different results, maybe its a hardware thing with tablets vs phones?

[rogerbinns]

What do you mean by limited? It has 1GB of RAM, a dual core 1GHz ARM processor, and just shy of a megapixel screen. As someone else calculated there are around 30MB of images. Quite frankly this should work out okay. (To my knowledge the iPhone platform tends to be skimpier on the memory. But then again there is less multi-tasking going on to soak up the extra.)

IIRC there was some past differences in iOS versus Android. Something like iOS prerenders the page to series of tiles so that as you scroll around it is really just showing tiles (think of how Google Maps works) while Android has a display list that is culled to the viewport and then (re)drawn as appropriate. But both sides were updating and changing how they did things.