Slashdot Mirror


Google's Definition of 'Open'

An anonymous reader writes "One of Android's biggest draws is its roots in open source. It enables a broad range of device manufacturers to work from the same code base, and provides app developers with more insight into the platform they're building on. But openness isn't a binary condition — there are many shades of gray. While Android is technically very open, from a practical standpoint it's much more difficult for device makers to distance themselves from Google, if that's their preference. 'Phone manufacturers and carriers that want to use Google's services must conform to Google's device standards, a stricter requirement than what basic AOSP requires. For some, this is a catch. For others, it's merely the cost of doing business. ... [Dianne Hackborn, one of Android's tech leads,] defends Google's right to include proprietary services, and to keep them proprietary, saying that its no different than any other proprietary app on Android. That's not entirely true, since Google does keep some API development to itself, but to its credit the company does open-source most of the new APIs introduced to Android.'"

16 of 168 comments (clear)

  1. Excelent read on Ars tech. by Anonymous Coward · · Score: 5, Informative

    Google’s iron grip on Android

    Great story how Google gets it grip on Android.

    1. Re:Excelent read on Ars tech. by Anonymous Coward · · Score: 3, Informative

      Great story how Google gets it grip on Android.

      However, as a counterpoint, here is a far less histrionic story which shows that AOSP is growing FASTER than Goog'es own Android, and has already easiy eclipsed iOS market share. Not to mention Nokia's Normandy phone, to be released later this month running a forked version of AOSP matched with Nokia serices rather than Google ones.

      ABI Research reports that Android once again dominated the Q4 2013 shipment numbers for smartphone advanced operating systems with 77% market share of over 280 million smartphones shipped in Q4 2013.Nearly one billion smartphones were shipped in 2013, Android accounting for 78% across the year.

      Android’s dominance is not quite as rosy as it seems though, with most of the growth coming from forked Android operating systems (137% year-on-year), mainly in China, India, and adjacent markets. Forked Android or AOSP accounted for 25% market share with 71 million unit shipments, as opposed to certified Android’s share of 52%, of a total of 77% market share.

      https://www.abiresearch.com/pr...

      For some reason, there's a concerted campaign happening to try to convince people that Google has locked up Android. It's an odd thing to pretend, and I'm wondering what their motive is?

    2. Re:Excelent read on Ars tech. by rudy_wayne · · Score: 3, Informative

      However, as a counterpoint, here is a far less histrionic story which shows that AOSP is growing FASTER than Goog'es own Android

      Except you left out the part that says AOSP is growing faster than Google Android only in China and India.

      As for the Ars Technica article, it's not histrionics to state facts:

      Google apps—mainly Gmail, Maps, Google Now, Hangouts, YouTube, and the Play Store -- are Android's killer apps, and manufacturers want these apps on their phones.

      While it might not be an official requirement, being granted a Google apps license will go a whole lot easier if you join the Open Handset Alliance. The OHA is a group of companies committed to Android—Google's Android—and members are contractually prohibited from building non-Google approved devices. Joining the OHA requires a company to promise to not build a device that runs a competing Android fork.

      Acer was bit by this requirement when it tried to build devices that ran Alibaba's Aliyun OS in China. Aliyun is an Android fork, and when Google got wind of it, Acer was told to shut the project down or lose its access to Google apps.

      This makes life extremely difficult for the only company brazen enough to sell an Android fork in the west: Amazon.

      Since the Kindle OS counts as an incompatible version of Android, no major OEM is allowed to produce the Kindle Fire for Amazon. So when Amazon goes shopping for a manufacturer for its next tablet, it has to immediately cross Acer, Asus, Dell, Foxconn, Fujitsu, HTC, Huawei, Kyocera, Lenovo, LG, Motorola, NEC, Samsung, Sharp, Sony, Toshiba, and ZTE off the list. Currently, Amazon contracts Kindle manufacturing out to Quanta Computer, a company primarily known for making laptops. Amazon doesn't have many other choices.

    3. Re:Excelent read on Ars tech. by 0123456 · · Score: 5, Insightful

      Except you left out the part that says AOSP is growing faster than Google Android only in China and India.

      So, only in the two (potentially) largest markets in the world, then?

  2. So, don't use Google Apps by Virtucon · · Score: 4, Informative

    You can use other apps and app markets on your android device. You don't have to use Google Search, Maps or Mail because there are free or very low cost alternatives to them and they don't have the clingy, Google scam you out of your data smell. Getting rid of them is a snap in most cases and there's literally dozens of websites that can help you do it. Sure when you get an "update" from your phone maker you'll probably get them all back again but it's easy enough to remove them or you can go with something like Cyanogenmod and never worry about it again. There are alternative AOSP based distros out there that don't have that Google smell so look around, It's really not that hard. If you've never rooted your phone or sideloaded an app or changed the OS it can be somewhat intimidating but you can also find help out there online and via local phone store kiosks (forget the pimple crowd at the Sprint, Verizon or AT&T stores) who can set you up in no time.

    I do have to say that the nicest thing about Android based phones is that there are alternatives. For example, I don't have Google Apps and use Skobbler for the navigation. It uses OpenStreetMap and I recently downloaded a couple of countries and really like the fact that I could navigate, offline.

    --
    Harrison's Postulate - "For every action there is an equal and opposite criticism"
    1. Re:So, don't use Google Apps by Anonymous Coward · · Score: 4, Insightful

      Bullshit article once again. It's almost as insane as the Ars article that I read on the subject (how could I avoid reading it when Ars' staff has been spamming its links all over the place)

      distance themselves from Google, ... that want to use Google's services

      Editors - are you so fucking blind as to not see the blatant contradiction here?

    2. Re:So, don't use Google Apps by elwinc · · Score: 4, Interesting

      Agreed. For me, the big draw of standard Android is maps/navigation/traffic. Decent speech recognition is the cherry on top. Being able to whip out my phone and say "navigate to airport" is worth a lot to me. The premise of the original article, "One of Android's biggest draws is its roots in open source" just doesn't ring true for me. In fact, I doubt it's true for the vast majority of Android users. I would suggest that Android's biggest draw is the price vs feature tradeoff. I'm aware that we aren't getting the main google apps for "free" but for many people they are getting them at an acceptable price.

      --
      --- Often in error; never in doubt!
    3. Re:So, don't use Google Apps by jader3rd · · Score: 5, Insightful

      The premise of the original article, "One of Android's biggest draws is its roots in open source" just doesn't ring true for me. In fact, I doubt it's true for the vast majority of Android users.

      That's true, but it kind of hurts the original Android fans. That's exactly the thing that got a lot of the early Android fans (especially the ones on Slashdot) to excited about Android. They went around telling everyone they could have a chance to talk to, to switch to Android. Their motivation was that Android was an Open Source device operating system, but knowing that no one cares, they just said 'It's better'. Now that Google has made a lot of the Android experience not fit the classic Open Source model, these early fans are feeling a bit betrayed.

  3. Works for me by rsilvergun · · Score: 4, Interesting

    Until Apple burst on the scene Carriers locked their platforms down, charged insane amounts of money for dev kits ($20k+) and were generally jerks to their customers. They had little or no desire to improve since they were making lots of money selling slightly better handsets and super high prices. Google does a good job reigning that in. The carriers aren't powerless in this equation either you know. I like that they're all at each other's throats :P.

    --
    Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
  4. Didn't stop Amazon by AmericanBlarney · · Score: 5, Interesting

    With the Kindle, I think the Amazon has been one of, if not the most, successful at embracing what Android provides as a core, but extending/customizing it to support their preferred business model. Sure, they did a lot of work on their fork of Android, but if other companies aren't willing to put the work in, don't complain about something you're getting for free.

    1. Re:Didn't stop Amazon by Anubis+IV · · Score: 5, Interesting

      Amazon is a success story here, but it's also a cautionary one. When most people envision an "open" Android, they envision a world where up-and-comers are capable of disrupting the old guard, yet the reality is anything but that. Instead, what we see from Amazon's example is that the cost of entry for launching your own fork is owning an established media delivery system, having an already-established app store with tens of thousands of apps available from day one, and having a world-class backend on which to build alternatives to Google's services.

      Who else has the resources to do something like that right now? By my count, no one. Microsoft would be the closest, since they have Azure and an established media content ecosystem, though they'd lack for Android apps. Sony? They lack for apps as well, though they're a possibility, since they have a media ecosystem and backend built up around their Playstation brand, which has tens of millions of users. Samsung? Probably not. They don't have the sort of ecosystem or services that could pull people away from Google.

      The point is, while Android itself may be open, it's not truly open to anyone but the biggest players in the game, so long as the most valuable parts are kept locked away by Google. The problem isn't that Amazon had to do "a lot of work on their fork of Android", the problem is that they had to do a lot of work establishing themselves in those other areas for years in advance before that fork of Android could even possibly be considered viable.

  5. Google Play Services by cseg · · Score: 4, Interesting

    Honestly, in my opinion the most offending point of Android is Google Play Services. Google making all its services depending on one another is something we've all been seeing for years now, one could argue that we're expecting and used to it. Now, a service at the center of it all, which can do anything it wants, whenever it wants, that's honestly going too far in my opinion.

    That's point #1, actually.

    #2 is the fact that for many people (myself included), the days of tinkering with devices is over. It can be a hobby sometimes/for some people, but I for one like to separate what I rely on from what I play with. So at best an Android device would be a toy, not something I rely on daily.

    Now, if anyone can point me to a simple/reliable way to use Google's Android without Google Play Services owning the device, and without being forced to nurse custom/specific distros/ROMs for it, I'd greatly appreciate it.

  6. Re: Make it complete without Google apps by hawguy · · Score: 3, Informative

    Please, one of the big ones needs to be our knight in shining armor and make an Android phone without all the Google tie-ins. Make your own app-store that doesn't require a login or GUID from users, only from authors. Make a map and navigation app based on OSM. Include offline calendar and to-do lists, with optional syncing to a computer or an open source online service. Resist the urge to replace Google's apps with your own proprietary apps. Just make a phone worth buying.

    You mean a Kindle?

    Or you can just buy a phone that has good Cynogenmod support and stick with the F-Droid open source app repository.

  7. Lack of Understanding of Open Source by Luthair · · Score: 4, Insightful

    Its almost like there is a concerted campaign this month against Android openness - or are journalists seeing buzz around earlier stories and creating more link bait? I think this article and the others all demonstrate a fundamental lack of understanding of the open source world.

    There is more than one model, while there are entirely open projects like the Linux kernel, there are also a great many projects with both open and proprietary components. See MySQL, JBoss, Glassfish, Solaris, ExtJS, Nexus, etc., all of these projects are completely functional products but the companies provide additional functionality for profit.

    Android code is available under an OSI license, the code comprises a complete functional product (assuming device drivers, but that isn't Google's responsibility). The Open Source world is driven by contributing back, not by getting everything on a silver platter for free.

  8. I guess the "Android fragmentation" FUD failed by whoever57 · · Score: 4, Insightful

    Only a little time ago, there was lots of "OMG Android is becoming fragmented" stories. Now the stories are essentially the opposite: that device makers are closely tied into what Google does.

    Is there someone behind this? Or am I seeing consipiracies where there are none?

    --
    The real "Libtards" are the Libertarians!
    1. Re:I guess the "Android fragmentation" FUD failed by swillden · · Score: 3

      Only a little time ago, there was lots of "OMG Android is becoming fragmented" stories. Now the stories are essentially the opposite: that device makers are closely tied into what Google does.

      Is there someone behind this? Or am I seeing consipiracies where there are none?

      It really has changed, and the first thing caused the second.

      Android fragmentation was becoming a real problem, so Google decided they had to do something about it. Since AOSP is truly open source, Google can't use it to control what device manufacturers do. Google's solution was to tighten up the licensing requirements on the Google Apps, requiring licensees to agree not to do things that tend to fragment the ecosystem. Similarly, many new APIs have been added to the Google Play services, rather than the core OS, because that way Google can push the new APIs out, rather than having to wait for carriers and device makers to upgrade the core OS.

      (Disclaimer: I'm a Google engineer, but I don't work on Android and don't have any knowledge of Google Apps licensing beyond what I read in public articles. My information about the intent behind putting APIs into Google Play services came from a talk at Google I/O last year.)

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.