Live data from Hacker News

Introducing Chrome for Android

googleblog.blogspot.com

211–220 of 240 posts

Re: Introducing Chrome for Android

#211

Earlier quoted context omitted.

I'm hoping this means it will get updates every 6 weeks, too.

yes it will.. > There will be the same 6-week release cycle for new versions, Pinchai says. http://parislemon.com/post/17215781807/chrome-for-android-th... but i would ask will they be automatic or manual?

Probably automatic, like all their other apps on Android. But you should be able to easily turn that off just like with all the other apps in the Market.

Re: Introducing Chrome for Android

#212
post #209
post #56

And in typical Google fashion, they have assumed that devices have an infinite amount of memory: https://imgur.com/zkh7C (this is with the app in the background!)

this might be because: - its loading its own webkit/js lib - it might be multiprocecss (is it?) I'm wondering how much firefox nightly uses on your phone

Look - as I said in my other comment, the issue isn't that it uses a tonne of memory. The stock browser does so too. The issue is that it is using that memory in such a way that it is evicted too late. The app is multi-process, but they're putting background services in the wrong process - they run in the main process that you'd expect to be heavy on memory usage. So instead of the memory-heavy UI stuff being evicted shortly after the UI goes away, it is evicted after all other background (multitasking) processes - including the launcher - have also gone away.

Note that my screenshot shows the active (i.e., not background processes that can be thrown away at any time) section of the running processes screen.

Re: Introducing Chrome for Android

#213

"Swipe from the edge to switch tab" is beautiful :)

It's something I've been asking from Google for a while. They need to implement swipes and gestures like that throughout the OS, and get rid of the bottom buttons which I think are wasting space.

Re: Introducing Chrome for Android

#214
post #84

Earlier quoted context omitted.

Why bigot your statement with such a ridiculous lead-in? On my Gingerbread device the browser right now, in the background, is using 67.15MB. What does that demonstrate? Nothing, given that the RAM was available and web browsing is one of, if not the most, complex activities you can do.

I should have qualified my statement by mentioning that the Chrome app process runs a couple of background services - this causes it to be killed for low memory after normal background processes (the actual behaviour is a little more complex than that, but that's the gist of it), which could potentially impact the performance of multitasking. The proper thing to do is to run background services in a separate process…

The comment I was referring to is under this G+ post: https://plus.google.com/105051985738280261832/posts/intiB73F...

Re: Introducing Chrome for Android

#216
post #16

Decoupling the browser from the OS is one of the best things that could happen for android security going forward. While it won't help people who can't get upgrades to ICS, at least it will solve the future problems of people who get stuck on 4.x while their OS browser slowly becomes more and more exploitable. I have one phone that is still on 2.2 - it is trivially easy to own the phone with a little bit of javascrip…

Nothing is stopping you from using another browser right now.

There are not that many browsers to choose from, but you could for instance download Opera Mobile - the next time you open a link you will be asked which browser you want to use. You should also be able to replace the browser on your home screen, although how easy it is might depend on what kind of launcher you have.

Re: Introducing Chrome for Android

#217
post #126

A browser with that many permissions? what good is sandboxing and everything if the browser can access 100% of my device, including microphone? i'm thankful this is not available for my ancient, 11mo old, nexus one.

Can we please stop with the hyper-generalization that is that each permission is being used for the app 100% of the time for everything? In almost every instance, one permission or another is required for some trivial task, and they add up quickly.

Re: Introducing Chrome for Android

#219
post #150

Earlier quoted context omitted.

It's apparently a feature: "An issue that often pops up for mobile browsers is that text on the website may be too small to read properly. Where the Android Browser employs a text reflow algorithm to clarify the situation, Chrome for Android features a technique which we’ve called Font Boosting. It uses an algorithm to increase font sizes when necessary, aiming to make the text readable regardless of the zoom level."…

Then their algorithm isn't consistent, as shown by screenshot. Some comments on HN are "boosted", while others remain tiny. This also makes it impossible to reliably hit any of the other page controls, like voting, without having to manually zoom way in and then back out.

Keep in mind that it's a beta

Re: Introducing Chrome for Android

#220

Earlier quoted context omitted.

You could always download an alternative browser, such as Opera.

Opera Mobile is awesome. It feels so much faster than the stock browser. I recommend it to anyone stuck on 2.2/2.3 for the foreseeable future (like me).

It's especially valuable on slow networks (or if you have limited data) due to its "turbo" feature.
Post reply on HN