Linked by Thom Holwerda on Sun 10th Feb 2013 21:07 UTC
Google "No, there's only one area where Android falls really, horribly, undeniably short when it comes to the tablet form factor: The web browser. It's the most fundamental tablet app, IMHO, and yet the web experience on Android could not possibly be worse." This, right here, is it. On my Nexus 7 - there's not a single decent web browser. Not one. The stock browser? Crashes a lot. Chrome? Slow, touch-unfriendly UI, laggy, and locks up all the time. Everything else uses non-standard UIs are, are plain buggy, are also slow, or any combination of the three - and yes, this includes your favourite browser. I've been through them all. Just yesterday I loaded up my iPhone 3GS, and Safari was like a dream. Internet Explorer 10 on Windows Phone 8? Buttery smooth and excellent UI. How Google - a web company - can let this situation persist is beyond me.
Thread beginning with comment 552067
To read all comments associated with this story, please click here.
by vivainio on Sun 10th Feb 2013 21:09 UTC
Member since:

At least in theory, it should be possible to do straightforward port of webkit2 rendering engine to Android, giving similar performance to iOS. I don't understand why this is not happening.

Reply Score: 1

RE: Webkit2
by Carewolf on Sun 10th Feb 2013 21:27 in reply to "Webkit2"
Carewolf Member since:

iOS does not use WebKit2, they have an old fork of webkit tree and uses a heavily modified WebKit1 layer.

On top of that. It is not quite straightforward to do a new WebKit port. To get something stable and good, it is at least a year worth of work for a team of 10 very good developers.

If you do want WebKit2 on an android device though, you can checkout the Snowshoe browser, which uses the QtWebKit's WebKit2 API QQuickWebView. It is still a under development, but looks very nice.

Edited 2013-02-10 21:31 UTC

Reply Parent Score: 2

RE[2]: Webkit2
by vivainio on Sun 10th Feb 2013 21:33 in reply to "RE: Webkit2"
vivainio Member since:

Turns out you are right; I got misled by the initial quick googling:

Reply Parent Score: 2

RE: Webkit2
by Kochise on Sun 10th Feb 2013 21:53 in reply to "Webkit2"
Kochise Member since:

Opera Mini and Mobile ain't good either, they don't use the desktop 'Presto' engine, which is more and more crash prone while being somewhat pretty decent IMHO. However since Opera decided to ditch out their internal web and javascript engine for webkit, I don't know what gonna make a difference in the long run.


Reply Parent Score: -1

RE[2]: Webkit2
by WereCatf on Sun 10th Feb 2013 22:06 in reply to "RE: Webkit2"
WereCatf Member since:

Opera Mini and Mobile ain't good either, they don't use the desktop 'Presto' engine, which is more and more crash prone while being somewhat pretty decent IMHO.

I have absolutely no complaints about Opera on either my tablet or my phone -- it's fast, stable and certainly more suitable than many (any?) other browser. I have not had a single crash with it, either, yet I've been using it on a daily basis for, well, whenever the hell I got my tablet. Must be around 2 years by now.

As for the article: Opera Mobile looks out-of-place, that is true, as it does not follow the UI-conventions set out by Google. But well, does it have to follow them, anyways, if the way it behaves and looks now works better? This in mind I just cannot agree with Thom's assessment that any and every browser other than Safari or IE is a horror to use.

Reply Parent Score: 12