jQuery Forum

Android devices are, of course, inconsistent and all different. I wouldn't make any judgment on performance based on Android devices. Use iPhone as a baseline, and realize that some Android devices will stink more than others.

1.4.3 listview performance is much better than 1.3. "No listview" performs even better! (Just make a simple list with your own CSS.)

Those performance tips are pretty old. Many aren't relevant to 1.4.

BTW, the developers generally don't read this forum. It's here for us to discuss and rabble-rouse, but, ultimately, if you want something to change, you need to raise an Issue on GitHub.

I thought it was part of the forum where the developers take a look. Thank you for the clarification. 

It is true that Android are all very different, but I thought that using a smartphone located in the middle-range, I'd a good idea of the experience that may be present (if only all world own mobile dual-core, see better ^ ^) 

More you're right, jquery mobile made ​​enormous progress between each version. But as I could see by browsing interning there always a problem on some fluidity JQM widget. Only problem, it is, to advices to improve performance are not updates and do not really apply to new versions.

It’s time to forget that part of history.

For id I can see to improve, but I do not know if this will help. 

Img are not all present, let me explain, I show you the structure in the most complete case. 

This is a listview feed a db a list of news, so this is the users who post an image or not. There is only one position in the "ui-bar" div li which is all the time present (16px with an average size of 100kb) 

At first I try without img, it was the same thing. Slow and jerky. 

My multi-page document contains about 5 pages (really empty ==> injection Ajax). I try dividing it into several html file, the remaining the same, alas result. I use jquery selectors, $ ("# id"), mainly. I saw that it was the best thing since the id is unique. 

Div for "custom corner", I think already be removed to limit the hash of JQM. 

However its still greatly limit my opportunities for improvement, apart from alleviating the class JQM and use my own css.

For those still looking for the answer, I found a solution that is right up with it because it is really close to the native. 

In addition to all the prerogatives to have a smooth and clean code, I use Velocity.js develop a library for jQuery, no code changes just inserting the library. 

That's great

While I would recommend this - or a similar solution - if you intend to make heavy use of jQuery's animation functions. (Better yet, use velocity.js or similar through it's native API, rather than using jQuery animation API as a wrapper...)

It's nothing specific to jQuery Mobile, though, and  I don't see how it would help with any of the issues above, though. It's an additional performance boost if you should be doing a lot of animation.

For most purposes, CSS animation works better/smoother than jQuery animation. jQuery animation was developed at a time when CSS animation did not yet exist. Much of it's purpose is gone. Javascript animation is still useful because it is more flexible than CSS animation, and there are good Javascript animation libraries - it's just that jQuery ain't one of them, and so this is a great solution if you are stuck with existing jQuery animation code.

jQuery Mobile uses CSS animation for it's page transitions, so using velocity.js would have no effect on them.