The problem with this is that it uses (http://fb.html5isready.com/) Safari a not UIWebView like phonegap+others. Javascript performance on UIWebView is much slower.
Our app is 'businessy' and truthfully it did work ok as html5 but there's definitely a speed difference. We wanted to give our users the best experience imaginable. FYI, many companies that went html5 have now gone back to native, not only FB but also Xero. http://thenextweb.com/dd/2013/03/18/accounting-software-startup-xero-ditches-html5-in-favor-of-native-ios-and-android-apps/ On Mon, Jul 1, 2013 at 12:23 PM, David Connors <[email protected]> wrote: > On Mon, Jul 1, 2013 at 12:08 PM, Craig van Nieuwkerk <[email protected]>wrote: > >> I have used PhoneGap in conjunction with www.vsnomad.com and it is >> pretty good. But you are essentially still dealing with a HTML5 app that >> has been wrapped in a native code wrapper. I used it with jQuery Mobile and >> there were quite a few performance issues that needed to be fine tuned. >> > > You also need to be clear on what your type of app is. If you're writing a > 'businessy' app with data display, query, etc it is probably fine. There > are guys out there who wrote a Fastbook (http://fb.html5isready.com/) > which proves the point for simple information display-oriented applications > (thought I think they prove that Facebook's mobile app is slow, not that > theirs is fast). > > If you're trying to write Bad Piggies, then HTML is a non-starter on > mobile devices. > > David. > >
