3 ms·
In my personal experience, jQuery Mobile has been incredibly slow (by incredibly, I mean hundreds of milliseconds of delay between touch events and response, wh
by 54mf 15y ago
In my personal experience, jQuery Mobile has been incredibly slow (by incredibly, I mean hundreds of milliseconds of delay between touch events and response, which is unacceptable to me) and is kind of ugly. It feels cheap to me. I wouldn't recommend it, but again, personal opinion.
You're right about the plugin system, but that also requires that you know Objective-C if you want to build anything on the other side of that plugin, and if you know Objective-C why are you bothering to build an app with PhoneGap?
Debugging in the browser is a possible solution, but even Mobile Safari's developer tools are very limited. The console displays more JS errors, but often won't include line numbers or other critical details. Plus, no support for any native hooks. Weinre is okay but you're right that it's still not as in-depth as a real browser, and I haven't been able to get it working on an actual device yet, only in the Simulator.
Basically, the whole environment still has that duct-taped-together feel to it. The benefits are still worth it to me, but there's definitely a lot of room for improvement.
- skol101 14y agoDefault settings aren't optimal, yes, but try looking around for answers on jQuery forum and Phonegap Google groups, and you'll find useful tips how to make interface more robust. E.g., for my links I use following code. It binds a tap event (instead of a standard jQuery Mobile click event) to a button/link, resulting in almost no delay. $('#footer-menu a').on('tap vmousedown', function () { window.location.href = $(this).attr('href'); });