The main focus of jQuery Mobile is NOT to be a competitor to native apps written in Objective C or even Sencha Touch. We aim to build touch-friendly UIs based on HTML5 for web apps and websites that are easy to build…
They were much buggier in 1.2 so 1.3 is much more reliable but your mileage may vary.
We're actually using hardware-accelerated CSS-based transitions based on jqtouch. The difference is that jqtouch doesn't scroll you back to the position you were on if you navigate back - you always scroll back to the…
What specifically is slow -- touch events, scrolling, transitions, etc? We're working on bug improvements on all of these items so things will get faster, lighter and more responsive as we go. Oh, and work on more…
It won't work right now but will when we get the major JS bugs worked out. Stay tuned. All other desktop browsers will work right now.
Yep, we're very active on our @jquerymobile twitter account since the team gained access to it a week ago. We'll be posting code updates and soliciting feedback so follow us. Sorry for the lack of communication over the…
We're working on debugging WP7 now and will be pushing an update soon to make things work much better. We use media query support to decide who should be enhanced and WP7 doesn't support these so we need to add some…
We're looking into every possible idea we can to shave file size and images down for mobile. Look for very aggressive use of CSS3 that falls back gracefully. We're hoping to eliminate all images (!) or radically reduce…
It's definitely a goal to support fixed toolbars but we're still looking at how to achieve this cross platform in a lightweight way because these can be pretty heavy. We may end up offering a lightweight version that…
Thanks for the positive feedback. You nailed what we were going for. Glad people seem to like the direction of the project!
The main focus of jQuery Mobile is NOT to be a competitor to native apps written in Objective C or even Sencha Touch. We aim to build touch-friendly UIs based on HTML5 for web apps and websites that are easy to build…
They were much buggier in 1.2 so 1.3 is much more reliable but your mileage may vary.
We're actually using hardware-accelerated CSS-based transitions based on jqtouch. The difference is that jqtouch doesn't scroll you back to the position you were on if you navigate back - you always scroll back to the…
What specifically is slow -- touch events, scrolling, transitions, etc? We're working on bug improvements on all of these items so things will get faster, lighter and more responsive as we go. Oh, and work on more…
It won't work right now but will when we get the major JS bugs worked out. Stay tuned. All other desktop browsers will work right now.
Yep, we're very active on our @jquerymobile twitter account since the team gained access to it a week ago. We'll be posting code updates and soliciting feedback so follow us. Sorry for the lack of communication over the…
We're working on debugging WP7 now and will be pushing an update soon to make things work much better. We use media query support to decide who should be enhanced and WP7 doesn't support these so we need to add some…
We're looking into every possible idea we can to shave file size and images down for mobile. Look for very aggressive use of CSS3 that falls back gracefully. We're hoping to eliminate all images (!) or radically reduce…
It's definitely a goal to support fixed toolbars but we're still looking at how to achieve this cross platform in a lightweight way because these can be pretty heavy. We may end up offering a lightweight version that…
Thanks for the positive feedback. You nailed what we were going for. Glad people seem to like the direction of the project!