Slashdot Mirror
Google Responds To EU Antitrust Claims In Android Blog Post
An anonymous reader writes Earlier today the European Union released a Statement of Objection against Google, asserting that the search giant's dominance violating antitrust rules and Android products hindering equal opportunities for market access among its rivals. Google has now released an official blog post in response to the Commission's proposed investigation. Regarding its Android devices, Hiroshi Lockheimer, VP of Engineering at Android writes: "The European Commission has asked questions about our partner agreements. It's important to remember that these are voluntary—again, you can use Android without Google—but provide real benefits to Android users, developers and the broader ecosystem." He continues: "We are thankful for Android's success and we understand that with success comes scrutiny. But it's not just Google that has benefited from Android's success. The Android model has let manufacturers compete on their unique innovations [...] We look forward to discussing these issues in more detail with the European Commission over the months ahead."
The history of mobile operating systems shows that your preferred strategy is a losing strategy. Users DO come crying over it, and developers cry twice as much. J2ME was basically Android 0.1 and took this approach - it was just a bunch of API specs and then phone vendors could license different implementations, write their own, etc.
J2ME sucked. I know this because I tried to write apps for it. Literally every freaking phone had its own unique combination of stupid, obvious bugs that rendered key APIs unusable without enormous piles of hacks. J2ME developers theoretically wrote Java, but often used a C style macro preprocessor because so many hacks required different source code to handle.
Android learned from J2ME and took a different approach - one single reference implementation that everyone builds off and is not pluggable except in very small, tightly controlled ways. You can modify the reference implementation to your hearts content unless you want access to the Play Store, in which case you have to pass the "Compatibility Test Suite" for core OS functionality, and for some other kinds of things that are impossible to unit test (e.g. Maps quality), agree to ship the Google implementation. This saves developers from J2ME hell making users and developers happy, and still lets manufacturers tweak things that aren't covered by the CTS, like reskinning things.
I see no evidence the EU has any understanding of the delicate balancing act Android represents, or the history of mobile phone operating systems. I fear this will be yet another bull-in-china-shop scenario. On the other hand, if Google are doing things like what Microsoft used to do by saying "if you sell any Google-services phone you cannot sell any non-Google-services phone" then that'd be a problem that is correctable without hurting developers.
Google is moving more and more utilities to Play Services, which is not open source.
Play Services is not only about Google-related services, it is also about OAuth for instance.
Unknowing developers rely on Play Services, making their apps incompatible with pure-Android devices.
To solve this problem, an Open Source implementation of Google Play Services is being developed:
http://softwarerecs.stackexcha...
The same is true for a lot of other banks. Google has intentionally made sure that they control the app distribution channel,
* WinPhone: Apps MUST be downloaded from the Microsoft Store
* iPhone: Apps MUST be downloaded from the App Store
* Android / AOSP: Alternative stores are explicitly allowed, though off by default. Apps may be sideloaded through a bootloader, through USB, through the official play store, or through third party app stores like Amazon's or F-Droid.
How, exactly, is Google the bad guy here?