The Problem with Sencha Touch and PhoneGap
moneytoolkit.com
moneytoolkit.com
http://blog.johnmckerrell.com/2007/03/07/problems-with-safar...
Basically if you are at or near 100% CPU, Safari’s HTML parser silently fails to parse your HTML.
Additionally, we have found this is not limited to the innerHTML property; we have observed the problem to happen with the W3C recommended method Range.createContextualFragment.
EDIT: formatting and cleanup
This makes me feel like I have one hand tied behind by back when creating UI flow, and it's maddening.
The biggest reason it feels native is that I'm attempting very little imitation of the iOS interface chrome. Other than a menu bar at the top and some text boxes as needed, everything is touchable graphics. It doesn't look or act anything like a web page; for instance, the click "shadow" never appears, and you can't scroll the page out of bounds (although there's a WebKit input box bug with that, too).
"The title may present a slightly unfair impression. Not all of these issues have anything to do directly with the PhoneGap or Sencha Touch codebase, but are simply limitations of browsers, web-views and performance of mobile devices, though Sencha Touch / Phonegap framework does inherit those problems (and go to some lengths to work round the issues)"
But there are defects and issues in both PhoneGap and Sencha Touch that I mention. But I also recognise that they are both doing a good job on balance to further the cause.