Epic vs. Google: Google Loses

Original Article ↗ Hacker News Discussion ↗

A US jury found that Google holds monopoly power over Android app distribution and in‑app billing, and illegally used deals with device makers and major developers to suppress rival app stores. Commenters contrast this outcome with Epic’s earlier loss against Apple, probing why an “open” Android ecosystem triggered antitrust liability while Apple’s fully closed iOS model did not. Many expect appeals and possible Supreme Court involvement, and debate whether the ruling will lead to meaningful competition in mobile app stores or simply push platforms to lock down even further.

Overview of the verdict

  • Jury found Google has monopoly power in Android app distribution and in-app billing, illegally tying Play Store to Play Billing and using anticompetitive contracts with OEMs and large developers.
  • Key evidence: secret revenue-sharing and “Project Hug”–style deals with phone makers and big game studios to disincentivize or halt competing app stores and non‑Play billing (e.g., OEM revenue share, Riot halting its store, special terms for Spotify).
  • Epic sought rule changes, not damages; the judge will decide remedies.

Why Google lost while Apple previously won

  • Many posters are puzzled: Android allows sideloading and third‑party stores, while iOS is fully locked down, yet Google lost and Apple won.
  • Explanations given:
    • Google: jury trial with strong documentary evidence of active suppression of competition on an ostensibly “open” platform.
    • Apple: bench trial; Apple has no OEM licensing layer, claims App Store is an integrated product feature, and there was little evidence of backroom deals to block rival stores (they are simply technically forbidden).
    • Courts treat OS‑licensor ecosystems (Google, Microsoft in the 90s) differently from vertically integrated vendors (Apple, consoles).

Open vs closed platforms and perverse incentives

  • Many see a perverse lesson: if you’re slightly open and then secretly kill competition, you get punished; if you’re totally closed from day one, you may be legally safer.
  • Some argue Google is “punished for being open”; others reply they’re punished for using their Android/Play leverage to stop OEMs and devs from exercising that openness.

Monopoly, markets, and consumer harm

  • Debate over market definition:
    • One view: “Android app distribution” or “iOS app distribution” are legitimate antitrust markets; within each, the platform owner has a monopoly.
    • Counter‑view: the real market is “phones” or “mobile gaming,” where iOS and Android compete, so store control is just part of a product bundle.
  • Strong disagreement on whether the 30% fee harms consumers vs only developers; some say competition would lower effective prices, others say prices follow willingness to pay, not cost.

Remedies and future implications

  • Expectations for Google: bans on certain OEM/developer contracts, API parity for third‑party stores, possibly a Microsoft‑style consent decree and stronger support for alternative billing and stores.
  • Many anticipate appeals; some expect eventual Supreme Court involvement, especially given tension with the Epic v. Apple outcome and potential circuit splits.
  • EU DMA is frequently mentioned as a parallel track that will force Apple (and possibly Google) to allow alternative stores and sideloading in Europe.

Security vs freedom

  • One camp prioritizes locked‑down app stores as essential consumer protection, especially for non‑technical users and against malware.
  • Another camp argues current mobile models over‑sacrifice user freedom and device ownership; they want PC‑like sideloading, competing stores, and regulation against store‑level monopolies, even if that raises security risks.