Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Don't bother recreating the app with any native features unless you really need to. Having said that, I have also found that PhoneGap is extremely buggy with jQuery Mobile and nested lists (the back button didn't actually work, like it wasn't keeping a history). No guarantees it wasn't my/the other developer's fault (some other developer gave me the JQuery Mobile code) and I also can't say if it is a bug in JQuery Mobile or PhoneGap or if it extended past nested lists. I just rewrote the app using a native ObjC.

I'd personally just go with a native ObjC app that has one WebView pointing to your website and some sort of mechanism for detecting if the internet is offline and displaying a message. Or use the caching manifest on your site.



I thought PhoneGap basically was an ObjC app with a webview pointing at the site, no?

I definitely don't need any native elements. I would love to have the app be exactly the same as the site, provided the performance is reasonable.

(And you may already know this, but the caching manifest has quirky rules; it's harder than it should be to use on a real site.)




Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: