Seems like it's a bit of both: http://blog.mobtest.com/2012/05/heres-why-the-facebook-ios-app-is-so-bad-uiwebviews-and-no-nitro/ i.e. the slowness of the UIWebView but also some questionable network requests.
On Jun 27, 2012, at 5:00 PM, Anant Narayanan wrote: > On 06/27/2012 03:00 PM, Anant Narayanan wrote: >> On 06/27/2012 12:28 PM, Kumar McMillan wrote: >>> This is an unfortunate message that they're sending with this article. >>> I'd be willing to bet a few shiny pennies that the slow part is not >>> the "embedded web browser" but the actual GET/POST network requests ;) >>> If they're re-implementing those parts in Objective C they might as >>> well use JavaScript. Maybe there is more to it than that. >> >> No, unfortunately, embedded web views really *are* slow on Android & >> iOS. Apple doesn't give you the shiny JITed JS engine on WebViews, and >> the one on Android is derived from the default browser app, not Chrome >> (though that may change once Chrome gets a larger foothold on Android). >> >> -Anant > > _______________________________________________ > dev-webapps mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-webapps _______________________________________________ dev-webapps mailing list [email protected] https://lists.mozilla.org/listinfo/dev-webapps
