|
|
|
|
|
by Bjartr
3717 days ago
|
|
It's the second and third points that I take issue (with Google) on. The first seems a reasonable way to try to ensure that if manufacturers want to benefit from the ecosystem Google has built they have to provide users with the experience Google intended. Less than that can reflect poorly on Google if the manufacturer provided ecosystem integration is lackluster or even intentionally restricted. The other two points are problematic because they apply restrictions to business decisions the manufacturer can deliver independent of how those offerings do or do not rely on the ecosystem Google developed and are therefore Google leveraging its business position to reduce consumer choice in its favor. |
|
Like you I do potentially have a problem with the second point - depending on the details. I think Google has good technical reasons to take measures to prevent fragmentation of Android. Incompatible ecosystems arising would have very real negative consequences for the very competition that the EU is trying to protect. (as in, the only reason there IS competition amongst Android OEMs is because there IS an OS with strong compatibility protections). What I don't think they can do is level those protections at a whole company level - you can't say "Acer can't make a variant of Android if they are also shipping a phone with Google Services". Now I would be OK with it if there's real potential for harm to the ecosystem - if Acer is shipping the phones which are incompatible and claiming they run "Android", for example. But if they clearly fork it as a separate OS, put out their own SDK with separate APIs etc. then Google has no business telling them not to do it. So even this one I could go either way on depending on the exact details of the circumstances.