https://speakerdeck.com/u/hdragomir/p/fast-mobile-uis
It's still a long way to go from there, though.
I work on Pocket Island, at wooga.
But I believe that can only be achieved by not depending only on pure javascript solutions for all parts of the mobile app. Contrary to your inference in the slides.
I think your advice is perfect for offline webview implementations but that is only part of the problem when online service connections come into the picture, don't you think ?
I do talk a lot about loading assets and logic and how hard it is to actually get stuff across in a nice way.
I never say go pure javascript. What I say is that you don't need mammoth frameworks on top of javascript. We ended up depending on PhoneGap quite a bit in the end.
Thank you for the great comment
Now, perhaps it because I am testing on older hardware; however this is for good reason. I test based on hardware that my clients/target audience use - if they upgrade and they get a speed increase then that's a bonus - but until then they need to get the best possible experience given the hardware they have. I will use HTML5 for applications if I can get a reasonable return on investment by doing so, but usability is always number one - if it doesn't perform well then it may as well be thrown out.