We're still seeing the fallout from the European Commission's $5 billion antitrust fine against Google. Earlier this week, Google announced it would comply with the ruling by unbundling the Google Android app package, allowing OEMs to skip Chrome and Google Search in favor of alternatives. The catch is that, since ad revenue from these Google services was used to support Android development, Google will start charging OEMs that license Google apps but choose the unbundled route.
Now, thanks to a report from The Verge, we're getting an idea of just how much this more flexible app licensing scheme will cost OEMs. Citing "confidential documents" that were shown to the site, The Verge says Google will charge OEMs as much as $40 per device if they don't use Google's preferred Android setup. The pricing is flexible based on the country and the pixel density of the device's screen. The EU is split into three tiers, with the UK, Sweden, Germany, Norway, and the Netherlands in the most expensive tier. Lower-end phones in bottom-tier countries can cost as little as $2.50 per device. Android tablets, if any of those still exist, get their own pricing tier that is even across all countries and caps out at $20. It all sounds very complicated, but if we imagine this pricing structure applied to the $720 Galaxy S9 sold in the UK, slapping on the top-end $40 fee works out to a 5.5 percent price increase and a $760 phone.
That's not the only spot in Android OEMs' wallets Google will hit. If OEMs don't pre-install Chrome, the report claims OEMs will no longer get a share of search revenue generated by Chrome users. The report says the new rules will kick in February 1, 2019, which is strange given that Google's new licensing rules from earlier in the week start at the end of the month.
Google's licensing setup
These changes are all a result of the European Commission antitrust investigation into Android. That commission found that Google illegally used Android to dominate the search market. The ruling (which is still being appealed) required Google to change its Android licensing deals, and the commission slapped the company with the record-setting fine.
A commercial Android device ships with a mix of licenses. The core Android OS is free and open source. Anyone can take it and do whatever they want without Google's involvement. If you want to make a viable commercial device, though, you'll most likely want the Google apps. The Google app package includes things like the Google Play Store and Google Play Services—which unlocks access to the entire Android app ecosystem—and killer Google apps like Gmail, Google Maps, YouTube, and the Google Assistant. Typically these Google apps didn't cost OEMs money, but they weren't open source and they weren't free. If you wanted to license the Google apps, you needed to sign a "Mobile Application Distribution Agreement" (MADA) contract with Google, which came with a whole host of requirements and restrictions that the EU took issue with.
Under the old MADA rules, if you wanted one Google app, you had to take all of them. You could install competing apps, but Google had default placement requirements for its apps, like requiring a Google search bar on the home screen, having certain applications in the bottom home screen dock, or creating a "Google" folder either on the home screen or app drawer. If OEMs still want to follow all these old Google app rules—which are now optional instead of mandatory—it sounds like they won't be charged for the Google apps. If OEMs want to mess with Google's preferred setup and pick and choose apps, or not follow the placement requirements, then the fees will start. The whole system basically works out as another "tier" of Android licensing: there's the free tier with Google's preferred setup and all of the old rules, and now there's a paid tier with more flexibility.
It sounds like this is still all about making sure Google gets what Google wants from these Android OEMs. Previously, Google did that with a restrictive contract. Now that the EU has taken that option away, Google is using every other trick it can think of to keep its Android package intact.
[contf] [contfnew] 
Ars Technica
[contfnewc] [contfnewc]
