4 ms·
My own PhoneGap-based iPad app is going really well so far, practically indistinguishable from native, but for one thing: WebKit refuses to let you have manual
by lukifer 16y ago
My own PhoneGap-based iPad app is going really well so far, practically indistinguishable from native, but for one thing: WebKit refuses to let you have manual control over hiding and showing keyboards. (I tried filing a bug, and it was closed as "works as intended".)
This makes me feel like I have one hand tied behind by back when creating UI flow, and it's maddening.
- cmelbye 16y agoDo you have a link to your app? I'm really interested in seeing web apps that work similarly to native apps, I've yet to see a great example yet.
- greendestiny 16y agoI'm working on a phonegap app at the moment. I definitely wouldn't say it looks native - I haven't really tried for that - but it is fast. You do have to be very careful about performance issues, but phonegap does make it exceedingly easy to incorporate native code if that is required. I would say, purely as a limited anecdote, that jquery mobile and other frameworks just weren't really fast enough for the performance I wanted to see.
- lukifer 16y agoAre you using any Javascript plugins at all? Regular jQuery, Zepto, Backbone, etc?
- greendestiny 16y agoRegular jquery, jqote2, Kelvin Luck's jquery date picker, jquery autoresize plugin (though its not really working out so far) and all the phonegap javascript functionality.
- lukifer 16y agoAlas, it's still under development, several weeks away from release at best. The biggest reason it feels native is that I'm attempting very little imitation of the iOS interface chrome. Other than a menu bar at the top and some text boxes as needed, everything is touchable graphics. It doesn't look or act anything like a web page; for instance, the click "shadow" never appears, and you can't scroll the page out of bounds (although there's a WebKit input box bug with that, too).