Comments on: Running jQTouch in PhoneGap

By: Jussi Toivola

Jussi Toivola — Fri, 13 Nov 2009 00:56:09 +0000

To Sergio da Silva: Do you use a regular link ? If yes, try to capture ontouch event instead. Worked for me. Sometimes the normal links don’t work at all.

By: Sergio da Silva

Sergio da Silva — Fri, 30 Oct 2009 04:49:37 +0000

Thanks for the hint but it did not change anything for the web app I am currently working on.

I am using jQTouch and also experience intervals of 1-2 seconds when tapping on a link when using Phonegap here (using an iPhone 3G device) … definitely quite unresponsive from an end-user perspective.

The web app itself is at least twice as responsive as the Phonegap app.

This makes Phonegap pretty useless for me for the time being … unfortunately.

It would be nice to try to solve these issue as jQTouch + Phonegap are indeed an interesting approach to web app / native app development.

By: PhoneGap Up To Speed « iamcam

PhoneGap Up To Speed « iamcam — Thu, 29 Oct 2009 14:09:32 +0000

[...] can read Jesse McFayden’s post here. And if you’ll excuse me, I have an app to finish… Filed under: Tips, mobile [...]

By: Jesse

Jesse — Thu, 29 Oct 2009 10:30:25 +0000

Cameron, It still feels like it takes a long time between when you press a link/button and when you see the state change to active. This is still consistent with what I see in an app using a straight up UIWebView, so it is probably not a PhoneGap issue.

By: Cameron

Cameron — Thu, 29 Oct 2009 09:37:12 +0000

Thanks so much for looking into this and figuring it all out. I immediately saw a dramatic performance increase.

I noticed you used terms like “majority of the sluggishness.” Is there something else going on that you think might be contributing?

By: Stuart

Stuart — Thu, 29 Oct 2009 05:48:06 +0000

I just tested my app and it does perform much better when I set EnableAcceleration to false! Although it’s still a bit less responsive than the Mobile Safari version. Maybe there’s another tweak to get a bit more performance out of it?

By: Stuart

Stuart — Thu, 29 Oct 2009 03:25:59 +0000

That’s very good news!

Thanks for looking into this and finding a solution so quickly.

By: Jesse

Jesse — Wed, 28 Oct 2009 18:29:33 +0000

I will be checking in a better solution tomorrow. As for your questions Jonathan,
1) I am not sure, will have to test.
2) Yes, if EnableAcceleration is false, then navigator.accelerometer.watchAccelerometer() will fail. Although because of the way the JS is currently implemented, there will be an interval firing and calling your callback with bogus data.

Another thing I am looking at adding is a capabilities object that would carry info on what API’s are supported by the currently running host.

By: David Kaneda

David Kaneda — Wed, 28 Oct 2009 17:46:33 +0000

Can’t say thanks enough for looking into this. I’m also curious about Jon’s questions, but it sounds like a great fix for simple apps.

By: Jonathan Stark

Jonathan Stark — Wed, 28 Oct 2009 17:36:28 +0000

I will test this on my own, but for the benefit of other readers I thought I should ask:

1) Will setting EnableAcceleration to false prevent the UndoManager from displaying the Undo confirmation dialog when the user shakes the phone?

2) Will setting EnableAcceleration to false prevent navigator.accelerometer.watchAcceleration() from working?

TIA