my application relies heavily on ajax calls to pull data into pages.  I have some 10 pages altogether which are mainly placeholders adhering largely to the multipage boiler point template in the JQM documentation.  All ajax calls are routed through a single method.  

in the browser, there's no noticeable difference in relation to navigating between pages etc.

However, when running the application on an Android phone or an iPhone, I'm experiencing significant issues with JQM version 1.0.a4.1 and I think I noticed issues creeping in in 1.0a3 but fobbed them off thinking it was probably something I was doing or not doing.  Certainly, with JQM 1.0a4.1, the user experience is abysmal to a point where people have given up using it, whereas they were very pleased with the experience in JQM 1.0a2.

I've since regressed to JQM 1.0a2 and it's like unclogging a drainpipe.  It just flows.

There is no difference in any of the code, just purely swapping JQM/JQ versions.

Am I the only one experiencing this degradation in responsiveness through the iterations of JQM/JQ?

cheers

Matt