How Google Android increased its iron grip on - Computerworld.nl

Background – Google clothe the ‘open’ Android getting further and urges partners an expanding beam own closed apps and services. Is it abuse?

Freshly leaked documents confirm the impression that Google his grip on the Android ecosystem firms and simultaneously at all costs its own, often proprietary software and services pushes. So get open earlier versions, software partners and apps and services from rivals increasingly less likely. Computerworld takes stock and dived into the secret contracts.

and Android Open Handset Compatibility

imperative role of Google in the Android ecosystem has long been controversial. In 2011, The Verge delved into the matter according to court documents in the case between Skyhook and Google. From this it appeared that Google executives themselves dictate what conditions OEM partners must meet. Google has this different sticks behind the door, which can be.

, if need be beaten

Thus, the mandatory promise within the Open Handset Alliance to avoid forking, Android Acer which was rebuffed by his ambitions with an Android derivative of Alibaba very hard. Then there is the so-called Android Compatibility Test, which Google enforces a litany of specifications for each device. This Google Samsung and Motorola could compel dumping geolocatiedienst Skyhook, in favor of its own location service.

Google appbundel: take it or leave

A third pole is the contract manufacturers (OEMs) to (to) install Google apps. Mind you, this is so formal separation of the ‘open’ Android. The source code of it can indeed be used for a completely proprietary platform, such as Amazon does, and Nokia is reportedly working on.

But for Android partners (OEMs and service providers) is a bare Android device not an option (s). No one can order the Play Store (formerly Android Market) and YouTube it. Google makes it convenient to use by combining more than 10 different Google apps under a license that must have apps: Mobile Application Distribution Agreement (MADA), a secret document which was hitherto unclear exactly what Google stipulates. This week leaked two contracts.

Prominent

and default

This contract not only describes the list of ‘mandatory Google apps, but also how they should be prominently visible and, last but not least, the default app (as the default over any rival apps). For OEMs, so take it or leave it ‘prominent’ to install a package of Google services or nothing. Below the list of mandatory Google apps, as defined in the 2011-1012 Google MADA contracts with Samsung and HTC:

The list of mandatory Google Apps

There is also a list of ‘optional’ Google apps that the manufacturer may convert voluntarily and at their own discretion on mobile like Google Earth, Orkut and goggles. Google may modify at any other times both lists and expand in the contract. It is important that also the position of the compulsory apps is recorded.

Mandatory minimum visibility of the apps, and Google Search should default be.

own geolocation first

For example, the Search and Play Store app at least be visible on the window next to the default home screen. And, more importantly, two key Google services should default: the zoekapp and geolocatiedienst

.

Google’s proprietary Network Location Provider should be default. Skyhook and other geolocatiediensten are thus no chance.

is remarkable that the contracts differ. Where possible, Google will enforce its strict MADA license without compensation, such as HTC. But for a powerful partner like Samsung, which dominates the market and develops itself many alternative apps, Google is ready to spawn money. Partner How much is unclear, it is fixed by yet another secret contract, the “Google Applications Agreement”.

Google Samsung paid for the appbundel, but how much?

On the next page: The fourth pole lies in the Trojan in Android Play Services

.