After playing around with jqm I'm very impressed with the speed of creating apps with this.

However, the responsiveness/speed is not as good as it could be. It feels at least twice as laggy on an android 2.1 phone as a native app. And this is just the UI - not even considering delay from http requests. I think we all would love to have a user experience as close to native apps as possible - I'm sure doable!

Three main issues for me:

1) delay when clicking buttons. I've seen other threads on it, but haven't found a definitive answer. Has anyone managed to modify a3 to get rid of the 300ms or so delay? Found this Google blog post on the topic -  http://code.google.com/intl/ro-RO/mobile/articles/fast_buttons.html

2) slowness when scrolling up and down a list of content. Does jqm use native scrolling? It feels choppy - and I've only got about 8 items on the list

3) choppy slide transitions - this might be because the animations are not HW accelerated on android. So I've disabled the transitions - still a slight delay when changing views, even without any animation

If anyone has any tips or tweaks to improve performance, would be most thankful. I know jQm will get there eventually when it's out of alpha - but as it's open source, would be great to see if people have come with solutions that can be implemented now