8 ms·
Android KitKat ships without browser app. OEMs have to license Chrome
- AdmiralAsshat 13y agoAll the more reason for OEMs to start shipping with Firefox instead.
- chimeracoder 13y ago> All the more reason for OEMs to start shipping with Firefox instead. I would love it if OEMs started to do this. Unfortunately, I bet that most OEMs will just license Chrome, and if they decide not to do that, my money's on them creating half-assed proprietary browsers built around WebView before they turn to Firefox. Which is a shame, because Firefox for Android is young, but shows great promise.
- nevi-me 13y agoThe latter is still fine as the Android team is apparently working on a way of updating the webview without upgrading the device OS. So even the halfbaked browsers can still benefit from speed and security improvements
- gcb1 13y agothat part of the comment was nonsense. they can compile the stock browser just fine. i bet all that means is that they removed dependency on the stock browser from the base system. which is welcome for barebones images that want only one browser that is not the stock one.
- freehunter 13y agoFirefox for Android is slower and has more bugs than Chrome for Android, but I use it and love it solely for the add-on support. LastPass on mobile devices sucked until I found you can install the add-on in Firefox and use your normal browser. Adblock is nice for cutting down on mobile data use, too.
- darkstalker 13y agoDon't know what are you talking about, Firefox on Android is currently the fastest browser there. Chrome is slower and buggier on every new update.
- freehunter 13y agoMy main slowness/bug with Firefox for Android is the sluggish scrolling. When I move my finger, there's a small but noticeable delay before the page starts moving. I don't have this problem with Chrome on my Nexus 4. Like I said, I prefer Firefox for its desktop-like features. But in my experience, Chrome has a faster response in the UI.
- kllrnohj 13y ago> if they decide not to do that, my money's on them creating half-assed proprietary browsers built around WebView All of the major OEMs have already done that. They've been shipping their own browsers built on top of webview for years now. The only devices that ever saw Google's/AOSP's Browser were Nexus devices and those running custom ROMs. Being limited to WebView isn't a problem anyway - that's all the old Browser used. It's "just" a UI on top of WebView. Just like the majority of browsers in the play store are "just" different UIs on top of WebView.
- _wmd 13y agoSadly it's unlikely that this is how it would work. Most probably when you agree to license the Google Apps package it's an all-or-nothing affair, so if you want Play on your handset, I'm guessing you must take Chrome too.
- ville 13y agoMaybe they learned from Microsoft that is not good to ship a browser with an OS?
- UnfalseDesign 13y agoIf that were the case, wouldn't they also not ship it with Gmail, Google Maps, YouTube, Google Calendar, etc.
- Kylekramer 13y agoThey don't. OEMs have to license those as well. This is making the browser more like those services on Android, not less.
- gcb1 13y agogoogle is worse than microsoft when it comes to web control. the only reason for this is so they can decouple the browser from the system, so they can update the browser faster. or do you think they like that all those pre 4.1 devices (90%+) cant run their tracking-cookie-substitute or whatever?
- UnfalseDesign 13y agoDecoupling an app from the OS to update it faster is the reason they pulled the YouTube app from being shipped with iOS.
- kllrnohj 13y agoThe YouTube app that was being shipped in iOS previously was written by Apple, not Google. Google's YouTube app was never bundled with iOS.
- skyjedi 13y agoBrowser is still in AOSP, https://android.googlesource.com/platform/packages/apps/Browser/+/kitkat-release https://android.googlesource.com/platform/packages/apps/Brow...
- d0nk 13y agoThis seems a bit odd to me. The browser is still in the AOSP source (platform/packages/apps/Browser) and has 4.4_r1.2 tags. It was also included in a self-built rom for my Nexus 4 without doing anything to explicitly include it. Even if google doesn't ship a browser in the source they provide to OEM's, the source for the AOSP browser is still readily available and trivial to add to the build.
- forgottenpass 13y agoAre the additional terms for licensing Chrome beyond what was already needed for OEMs to get the Play Store? Unless there are and they're onerous in particularly new way, this feels like a non-issue getting attention because the business agreements around Android are relatively public compared to other OSes.
- shooper 13y ago>this feels like a non-issue getting attention because the business agreements around Android are relatively public compared to other OSes. Are they? Where can we see them? The page at [1] about the Open Handset Alliance contains a lot of noise about openness etc. but there are no details of the agreements or how much it actually costs for a Google apps license. I remember everyone was surprised when Google forced Acer to pull phones based on Aliyun OS because of the OHA agreement, which IIRC, is under NDA and secrecy. [1] http://www.openhandsetalliance.com/oha_overview.html http://www.openhandsetalliance.com/oha_overview.html
- Oletros 13y agoWhat has to do OHA with Google Apps?
- deleted 13y ago[deleted]
- billyjobob 13y agoChromium is a free software version of Chrome for PCs. Is there an Android version of Chromium? If so, wouldn't OEMs just ship that instead of licensing Chrome?
- jsight 13y agoThe browser that is included with Android 4.4's source code is Chromium. This is still available. I'm not really sure what the author is trying to say, but it seems like an inaccurate article to me.
- kllrnohj 13y agoSort of. Chromium is actually the base for Chrome, and that's true for Android as well. However while Chromium on PC has more or less the complete browser UI, the Chromium for Android does not. All the hard stuff is there in Chromium for Android - blink, V8, graphics, webgl, etc... - but the UI isn't. In Android 4.4 the WebView sits on top of Chromium, so if an OEM really wanted they could continue to use their own browser skins that sit on top of WebView like they previously shipped and it will now magically use Chromium under the hood. So really there's no story here.
- ozten 13y agoIf only there was a free, completely open source browser with more than 4.5 stars in the Google Play store which could be bundled without any business deals... Bonus points for a cool project codename like Fennec.
- sp332 13y agoFirefox for Android hasn't been called Fennec for a long time :)
- TazeTSchnitzel 13y agoThey said "codename", to be fair.
- raverbashing 13y agoWell, I'd say one advantage of the "store" model is that you don't need a browser to download a new browser (well, in the back it probably has a lot of Webviews, still)
- bostik 13y agoI think I'm going to make a bet against myself. I have a feeling that in 2-3 years' time the play store app will be phased out and integrated with Chrome. From thereon, if a vendor wants to call their device an Android[tm], they'll have no choice but to ship a browser they no longer control in order to have access to Android app arketplace. I'm not sure if this is laying groundwork for a pre-emptive strike against competing marketplaces or just an attempt to unify the browser experience for all future Androids. Could be both. They are not mutually exclusive.
- chris_mahan 13y agoChromeOS on Android on Linux?
- mbennett 13y agoIf only there wasn't an agreement prohibiting such replacements. Bonus points for calling it the "Open" Handset Alliance agreement. http://www.theverge.com/2011/05/12/google-android-skyhook-lawsuit-motorola-samsung/ http://www.theverge.com/2011/05/12/google-android-skyhook-la...
- driverdan 13y agoIs Google making companies pay for software they offer as a free download in the Play store? How does that make any sense?
- Zigurd 13y agoBefore Chrome became the Android browser id led a dual life, as Chrome, Google's commercial product that includes some licensed IP, and Chromium, an open source project. I expect that licensing Chrome in Android is necessary for the same reasons there are parallel projects and products for other platforms.
- Aissen 13y agoOne thing that isn't in the article: Chrome for Android is proprietary software. Yes it uses the chromium project as an engine, but all the UI bits are proprietary. This leads to ridiculous procedures if you want to recompile libchromeview.so and replace it in your app: http://code.google.com/p/chromium/wiki/AndroidBuildInstructions#Rebuilding_libchromeview.so_for_a_particular_release http://code.google.com/p/chromium/wiki/AndroidBuildInstructi...
- neltnerb 13y agoFunny, this is exactly what Microsoft was sued over =) Good on Google for pre-emptively removing vendor lockin for browser choice.
- drzaiusapelord 13y agoThis is fud. Browser is still in AOSP. Pretty sure this is it here: https://android.googlesource.com/platform/packages/apps/Browser/+/kitkat-release https://android.googlesource.com/platform/packages/apps/Brow... Obviously you can create the gui for a browser to access the webkit renderer if you didnt want this. Anyway, this is meaningless. No one ships commercial phones without the Play store and Chrome will be just another app bundled with the deal.
- Timmmmbob 13y agoYes, the truth is that the AOSP Browser is now abandonware - Google have stopped developing it in favour of Chrome, and likely won't accept non-security patches for it. I don't think this matters much anyway. Firefox is a more than capable browser. Possibly better than Chrome on Android. It's certainly smoother.
- shooper 13y agoAlso, the Open Handset Alliance terms may prohibit OEMs from replacing Chrome with, say Firefox. From http://arstechnica.com/gadgets/2013/10/googles-iron-grip-on-android-controlling-open-source-by-any-means-necessary/3/ http://arstechnica.com/gadgets/2013/10/googles-iron-grip-on-... >Any OEM hoping to license Google Apps will need to pass Google's "compatibility" tests in order to be eligible. Compatibility ensures that all the apps in the Play Store will run on your device. And to Google, "compatibility" is also a fluid concept that an Android engineer once internally described as "a club to make [OEMs] do what we want." While Google now has automated tools that will test your device's "compatibility," getting a Google apps license still requires a company to privately e-mail Google and "kiss the ring" so to speak. Most of this is done through backroom agreements and secret contracts, so the majority of the information we have comes from public spats and/or lawsuits between Google and potential Android deserters (see: Acer). >Another point of control is that the Google apps are all licensed as a single bundle. So if you want Gmail and Maps, you also need to take Google Play Services, Google+, and whatever else Google feels like adding to the package. A company called Skyhook found this out the hard way when it tried to develop a competing location service for Android. Switching to Skyhook's service meant Google would not be able to collect location data from users. This was bad for Google, so Skyhook was declared "incompatible." OEMs that wanted the Google Apps were not allowed to use them. Skyhook sued, and the lawsuit is still pending.
- berdario 13y agoNot only the browser in AOSP is based on chromium, but it's also used as the webview engine itself... http://blog.chromium.org/2013/11/introducing-chromium-powered-android.html http://blog.chromium.org/2013/11/introducing-chromium-powere... as much as I despise Google for closing up a lot of bits of android, this doesn't seem much of an issue... also: every OEM worth its salt should just build their android from the AOSP (or some fork)'s sources
- nostrademons 13y agoSpeaking solely as a web developer: good riddance, the pre-KitKat stock Android browser is a piece of shit. It relies on an old fork of Webkit that has none of the features of the modern web, no GPU support, and a lot of outright bugs (like it would flip back to the first frame of a CSS3 animation right before the animation completes, creating an ugly flicker). Without this change we'd be left with Android Browser & clones as the IE6 of the mobile web. I'm hoping all the OEMs build their own browsers off the Chromium WebView that ships in KitKat; then at least we only have to worry about Chromium and Mobile Safari.
- icebraining 13y agoHey, some of us use Firefox.
- nostrademons 13y ago...which at least follows web standards fairly closely. Firefox is nearly as quick as Chrome at keeping up with the latest and greatest. Android Browser hasn't been updated in years.
- cpeterso 13y agoPlus, Firefox still supports Froyo and Gingerbread. Chrome only supports Ice Cream Sandwich and later. Android users with older phones have been abandoned by Google, but at least they can download a modern web browser.
- fidotron 13y agoBut speaking as an Android user, Android Chrome is a slow piece of crap, (with that horrible text resizing thing going on) while the stock browser actually works.
- nostrademons 13y agoI've been using Android Chrome as a user since it was in beta; it's been my default browser for at least a year now. I had far more problems with Android Browser than Android Chrome. (They are working on speed though; not much attention has been paid to performance optimizations besides using the GPU for animations.)
- thrillgore 13y agoIt's the IE/Netscape lawsuit all over again.
- icebraining 13y agoGoogle is actually doing the opposite of what Microsoft did: they're unbundling the browser from the OS. Which is not to say it's a good thing, just that it isn't the same at all.