Android tablets: It's the browser
21–30 of 73 posts
Re: Android tablets: It's the browser
#22My comparison is iPad Mini Chrome to Nexus 7 Chrome, have to agree that Chrome on Nexus 7 is not up to par with iOS. But I do strongly prefer Chrome's UX over Safari's. Primary issues with Chrome on Nexus 7: - Scrolling performance is much slower, especially while loading larger pages. - I have a much harder time opening links on the N7 on pages like HN front page where there are clusters of links with fairly small t…
Re: Android tablets: It's the browser
#23Bought two nexus 7 over christmas, one for me and one as a present. I've only read good things about them. Ended up returning them both due to the bad surfing experience. Laggy, bad scrolling. Sometimes it felt like it missed my swipe as a whole and just got stuck. Switched back to my ipad1 which is much better in that regard. I liked the rest... but surfing is what I do most on a pad, so that has to be perfect.
Re: Android tablets: It's the browser
#24I thought the article was a bit hand-wavy in general but that's something I agree with. I'm a die hard android user and I have this problem. Why do I have to make the choice for EVERY SINGLE BOOKMARK? Can't you remember that I open bookmarks in Chrome?
Re: Android tablets: It's the browser
#25My comparison is iPad Mini Chrome to Nexus 7 Chrome, have to agree that Chrome on Nexus 7 is not up to par with iOS. But I do strongly prefer Chrome's UX over Safari's. Primary issues with Chrome on Nexus 7: - Scrolling performance is much slower, especially while loading larger pages. - I have a much harder time opening links on the N7 on pages like HN front page where there are clusters of links with fairly small t…
In Chrome for Android beta they've implemented some changes that are suppose to improve scrolling, especially on large pages, and they've adjusted the tap disambiguation popup. If you don't want to use the beta these changes should filter down to the stable release at some point.
Re: Android tablets: It's the browser
#26Re: Android tablets: It's the browser
#27I agree for all Android devices until the current generation. However, with the Nexus 7, Nexus 4, HTC One X, and similar devices I find the Chrome experience to be every bit as good as iOS. Maybe I haven't used iOS long enough to catch the very small differences but I now consider the browsers to be equal. The only area in which iOS still wins is startup/resume time for the browser with a few tabs.
I would bet that the majority of Android smartphones -- the ones that aren't the marquee, top-of-the-line products -- all have a similar quality of experience with Chrome.
In a few years when Moore's Law catches up to the lower end of Android phones, that won't be an issue, but right now I think we're still in a transition period.
Re: Android tablets: It's the browser
#28And worse? It's not fixable by anyone outside the core team of developers as they've moved away from the standard XUL UI system to a pure Java wrapper. I was going to get in there and whip up some add-ons because I really wanted to use the browser and thought if I could just tweak a few of it's more ugly bits it'd be somewhat usable. But after downloading the code and taking a good long look, it turns out that all th…
Re: Android tablets: It's the browser
#29"2. This is the dialog box that comes up when I click a YouTube link in Reddit. I've chose "Always" about 3,496 times thus far and it doesn't seem to ever last for more than a day or so. Basically, any time any app updates it seems to reset your default choices." I thought the article was a bit hand-wavy in general but that's something I agree with. I'm a die hard android user and I have this problem. Why do I have t…
Having said that, it seems like he's running into a bug where it isn't saving this setting and I can see how in that case it would be hugely annoying to be asked this all the time.
I'm a pretty big Android fanboy and my day job is currently Android programming and I mostly enjoy it, but I've been kind of surprised at the number of "how did they never notice this" bugs that have been introduced in Android over the recent past, especially in the two Jelly Bean releases. It is entirely possible this bug we're talking about now is phone-specific and isn't a general Android bug (I've never seen it nor heard of it being a common problem), but the amount of bugs introduced into the core OS over the past couple of releases is somewhat worrying.