I think it's time to stop accusing webviews of being slow.
[1] scirra.com
I think it's time to stop accusing webviews of being slow.
[1] scirra.com
The dev team at my ex company built a demo to show that the same app could have been made to perform acceptably using the right strategies.
https://www.sencha.com/blog/the-making-of-fastbook-an-html5-...
Incorrect at least as far as Android goes. Android's WebView literally was the system browser until Chrome was released complete with the JIT since Froyo (V8) and hardware rendering since Honeycomb. And the first several versions of Chrome on Android had much worse performance than the old WebView did.
This aside the bulk of HTML content is still software-rendered. It's software-rendered into tiles which are then GPU composited. It's a different story if you use <canvas>, but at that point you aren't gaining much by paying the browser tax so why not just drop to C++ and write GLES directly and get like 10x the performance?
That aside while there have been improvements in JavaScript performance, HTML/CSS & rendering performance really has not improved much if at all over the years. Browsers are still dreadfully slow to actually produce pixels compared to any other UI toolkit.
It has a few limitations, but it's quite nice for games.
The Chromium based webview is available already in Android 4.4. So about 50% penetration at this point. It is indeed a huge boost to performance.
So that it's only 100 times slower than a native app instead of 200 times?