Supported HTML5 API's about mobile-chrome-apps

[shacharz]

I agree, Are there intentions to implement using Chrome?

[bshepherdson]

Mobile chrome apps are based on Apache Cordova, and both are forced to use
the system webview. (This is true even when you have Chrome for Android
installed.) Believe us, we would much rather be using Chrome than the old
Android webview. From KitKat 4.4, the webview is based on Chrome, and these
problems go away.

We mentioned indexed db because that's been the most-missed feature; you're
quite right that there's lots more missing from the old webview. It
wouldn't hurt to be more explicit about that in the documentation.

On Wednesday, January 29, 2014 5:15:25 AM, Shachar Zohar <
[email protected]> wrote:

I agree, Are there intentions to implement using Chrome?

Reply to this email directly or view it on GitHubhttps://github.com//issues/53#issuecomment-33571499
.

[shacharz]

So there's no hope in IOS, right?

[bshepherdson]

iOS Webview is nowhere near as buggy, slow, and lacking in support as the old Android Webview, but yeah, it's not going to be Chrome any time soon. Definitely take a look at http://caniuse.com and the iOS Safari and Android Browser columns for any features you're hoping to use. As I said, IndexedDB is easily the most high-profile gap.

[mmocny]

Crosswalk fixes a lot of these issues on Android.
iOS WebView is improving in iOS8 but there will likely always be some gap. Not much we can do about it -- but there are polyfil plugins for many of these apis that exist as cordova plugins. Quality varies, so we don't install them by default.