Remember too that an early goal of the thing formerly known as PhoneGap was to go way. We explicitly choose to not ship our own browser b/c we want developers to have a migration path back to the web proper (as rendered in web browsers) meaning that while, yes, there is more surface to content with it is not more than you'd have to live through where you shipping for the web.
We already are sort of our own weird user agent and I'd rather more diversity in rendering options than less. Embedding a version of Chrome or even Geckoview on Android is definitely in our sights and I would LOVE it if we had that same freedom (right?) to ship similar to iOS. On Tue, Oct 8, 2013 at 8:43 AM, Jonathan Bond-Caron <[email protected] > wrote: > On Tue Oct 8 11:19 AM, Jacob Robbins wrote: > > > > This made me wonder, has there been discussion of integrating a full > > mobile > > browser codebase into Cordova and using that instead of the > > native webview? > > Mozilla sort of went this way with XUL where you > > could take their HTML engine > > and use it in a non-browser context. > > > > Seems to me a lot of usability problems with non-native apps result from > > running them inside the same HTML engine used by the platforms' default > > mobile browser. The native browsers are moving towards features that help > > make regular websites accessible. Being a great virtual machine for > > non-native > > apps is not a high priority for them. > > > > +1000 > > Unfortunately, my understanding is App Store rules requires use of > UIWebView so don't think cross-platform is feasible > > But having this option on Android would be huge (same chrome view on > Android 2.x+), I'd pay for that option > >
