Live data from Hacker News

Introducing Chrome for Android

googleblog.blogspot.com

101–110 of 240 posts

Re: Introducing Chrome for Android

#101

"This item cannot be installed in your device's country"

It's currently available in: United States, Canada, United Kingdom, France, Germany, Spain, Australia, Japan, Korea, Mexico, Argentina, Brazil

Sundar, SVP of Chrome just said "We are working hard to bring this to more countries and should greatly expand within the next three months."

Re: Introducing Chrome for Android

#102
The blog post doesn't go into it, but I'm curious to know what the long-term implications of this release are for the built-in android browser and the android SDK's WebView and WebChromeClient.

If this is indeed the first step towards decoupling the browser from the Android platform itself, I would expect to see continuing development of those aspects of the SDK to dwindle and die completely, leaving them in the dust feature-wise when compared to native apps, and putting the people who work on web-wrapper-apps at an even more serious disadvantage.

Re: Introducing Chrome for Android

#103

I think is the death knell for ChromeOS. Android browser has always sucked, it was the primary reason I haven't bought an Android device. Google had the resources to make Chrome on Android a long time ago, so I presume they were dragging their feet in a "wait and see" approach for whether ChromeOS had any chance on its own.

I don't believe so, for both your statements :)

First off, this took so long because Chrome was built using a "normal" devel framework (gcc, make, etc) with a few added tools (repo, gyp). The UX for Chrome is provided via OS-specific graphical APIs, like X.org, Cocoa, and Win32.

Android uses a Java framework, which in turn contains the code that manages all rendering and UX, so not only did Chrome UX needed to be ported to Android's graphical API, but the entire build environment needed to be JDK compatible.

I agree the Android browser is laughable compared to Chrome, and Chrome on Android is the future, but there were so many developmental problems that needed to be solved first before one could stick to the other.

Regarding your ChromeOS comment, this has nothing to do with that as ChromeOS is designed to solve an entirely different problem. Many power-users (developers, technology bloggers, etc) seem to have a hate-on for ChromeOS because they're afraid it'll kill their venerable laptop. That will never happen. :)

ChromeOS is designed to kill those netbooks and laptops where common-users (my wife, for example) only use them for browsing gmail, facebook, and a few forums. 95% of what these users do are web based, barring a few native apps, of which NaCL and other HTML5 technologies are aiming to solve.

Re: Introducing Chrome for Android

#104
post #65
post #45

Earlier quoted context omitted.

Chrome and the old Android browser are both based on WebKit. Google will almost certainly make Chrome the default browser for new editions of Android, and will likely push for it on IOS and Windows phone.

Given that IOS is already on WebKit, there's no fragmentation here. WebKit has a monopoly on mobile.

The license doesn't allow a different browser on iOS unless it uses Apple's Webkit anyway. Opera Mini was a technical exception. Every other browser is Safari, just with a different chrome.

Re: Introducing Chrome for Android

#105

The blog post doesn't go into it, but I'm curious to know what the long-term implications of this release are for the built-in android browser and the android SDK's WebView and WebChromeClient. If this is indeed the first step towards decoupling the browser from the Android platform itself, I would expect to see continuing development of those aspects of the SDK to dwindle and die completely, leaving them in the dust…

That's a very good question indeed, especially since some seem to suggest that Google will eventually replace the stock browser with Chrome, and Chrome is proprietary.

Re: Introducing Chrome for Android

#106
post #67

Earlier quoted context omitted.

I ran 4.0 via Cyanogenmod 9 on my Nexus S 4G for weeks, and unfortunately the bugs and constant app crashes got so bad that, as much as it pained me to do so, I went back to 2.3 yesterday. I love Android 4.0, but there doesn't seem to be a good, stable implementation of it yet. Example issues: * Random reboots * Choppy playback in the Music app (Amazon MP3 worked fine) * Random app crashes, particularly games (possib…

I've been using this ROM on my NS4G for about a month: http://forum.xda-developers.com/showthread.php?t=1364221 In my experience, the stability and performance of various peripherals like GPS and the WiMax radio are about as good as the stock 2.3 ROM. I haven't even noticed a change in battery drain...

I'm running the same ROM on a NS4G also for about a month. It feels like a new phone and has been awesome in every way.

Re: Introducing Chrome for Android

#107

It doesn't seem to be available in Finland, found a apk at XDA tho: http://forum.xda-developers.com/showthread.php?t=1485420 Too bad, it instacrashes om my ICS GalaxyS

It insta-crashed for me too on my Samsung Fascinate with CM9. I cleared the app's data, its cache, uninstalled it and reinstalled it. It works like a dream now.

Re: Introducing Chrome for Android

#109
post #86

Earlier quoted context omitted.

Nobody uses Firefox Mobile.

Any factual statistics for that?

I've never seen any chart or graph where Firefox Mobile even shows up. Usually when something has http://gs.statcounter.com/#mobile_browser-ww-monthly-201101-...

http://www.netmarketshare.com/mobile-market-share

Re: Introducing Chrome for Android

#110

"This item cannot be installed in your device's country"

It's currently available in: United States, Canada, United Kingdom, France, Germany, Spain, Australia, Japan, Korea, Mexico, Argentina, Brazil Sundar, SVP of Chrome just said "We are working hard to bring this to more countries and should greatly expand within the next three months."

How hard it can be to tick a few checkboxes?
Post reply on HN