Android 4.4+ are based on Chrome/blink for the WebView but they deactivated the hardware acceleration for Canvas2D and removed WebGL support, as well as Web Audio API. [1]
iOS 4+ support WebGL in the webkit engine, but it's only enabled for iAds. [2]
[1] http://www.html5gamedevs.com/topic/1915-android-44-kitkat-in...
[2] http://en.wikipedia.org/wiki/WebGL and the related discussion https://news.ycombinator.com/item?id=7265230
> Chrome for Android supports a few features which aren't enabled in the WebView, including:
If Google was trying to protect the app-store walled-garden - surely that would mean the reverse? Currently in-browser games that bypass the appstore completely have access to more features than native apps?
It fits perfectly in the picture that Apple doesn't allow alternative browser engines. Chrome for iOS just embeds UIWebView and there is no Firefox for the same reason. The JavaScript JIT is disabled for UIWebView, and only enabled for Safari.app.
In an ideal world, one could write powerful HTML5 apps that run on Android, iOS, FirefoxOS and desktop browsers. And AppsStores would allow one to add an entry to the apps web URL or at least provide an non-crippled WebView so that one can write a simple wrapper app (or use phonegap/etc).
Right now I'm running WebGL apps on my Android phone, and in Chrome you can put web apps on your homescreen with a single click in the menu. You don't need to go through any store, and you can open it like any Android app from the homescreen.
What's more open than that?
The problem is not with web technology, but with the implementation and use of web technology. Of course, since this is mostly out of the hands of app developers, this doesn't help much. But I think it is important to be blaming the right culprits.
(Hopefully we are not too far off bringing these optimisations to Firefox on Android at least, for now they exist only for Firefox OS).
Not to mention you have so little control over device itself, only thing you can do is rely on Cordova plugins (which are horrible to begin with).
Never again.
Architecturally, it's really no different than a PhoneGap or web app running on Android, iOS or BlackBerry OS. They all involve an "app" typically written with HTML+JavaScript, executed in a web browser (often full-screen and without chrome), which in turn runs on an operating system of some sort.
If it's "native" on Firefox OS, then why isn't it just as "native" on Android, or iOS, or BlackBerry OS, or other mobile OSes?
What I think we really see is Firefox OS totally lacking any sort of real native software development support. This creates the illusion that web apps are somehow "native", when this is just a result of there being no other viable option.
There will never be access to run native binaries on a Firefox OS device. Web APIs are as close to bare metal that it will ever expose.
Seeing that as "totally lacking any sort of real native software development support" misses the whole purpose of the OS, because the web is native on Firefox OS.
The problem lies in how it is used. Our project tried to incorporate a ton of native UI/UX conventions that screwed us over royally. CSS transitions, layered divs, swipe gestures, all of these were far too complicated for a little phone to handle. Stay away from these, and do simple hides and shows. Or go the hybrid method of having barebones native wrappers and web-views inside of those views.
The web (i.e. HTML/CSS/JS) promises a lot but mobile browsers are nowhere near where they should be in terms of pure processing power. As of right now, native is still the way to go.