Google agrees to pay $700M in antitrust settlement reached with states
Google’s $700 million antitrust settlement over its Android Play Store practices is widely seen as a modest penalty compared to the estimated $10.5 billion in potential damages and the scale of its alleged anti-competitive behavior. Commenters debate whether the mandated changes—such as easing barriers and “scare screens” around third-party app stores—strengthen openness or merely expose less technical users to more malware risk. The case is also contrasted with Apple’s tightly controlled App Store, highlighting how antitrust law treats market dominance, platform openness, and security trade-offs differently across ecosystems.
Settlement Size, Deterrence, and Payouts
- Many see the $700M settlement as tiny relative to Google’s size and the states’ claimed $10.5B damages; viewed as a “cost of doing business,” not a deterrent.
- Several argue this shows U.S. antitrust remedies are toothless and encourage future anti‑competitive behavior.
- Consumers are expected to get very small payments (often cited as ~$2), with anecdotes of past tech settlements paying out cents via check.
- Some note the main financial winners are likely the lawyers, not users.
Android Openness vs Walled Garden Behavior
- Strong disagreement over whether Android is genuinely “open” or effectively a walled garden marketed as open.
- Critics cite Google’s contractual restrictions on OEMs, Play Store dominance, “scare screens” for sideloading, and steering developers into Play Services as evidence of controlled openness.
- Others counter that the ability to sideload and use alternative app stores (Samsung, Xiaomi, Amazon, F-Droid) still makes Android meaningfully more open than iOS.
Security, Sideloading, and “Grandma Getting Fleeced”
- One camp worries weakening warnings and easing third‑party installs will increase malware and scams, especially for non‑technical users and in regions where cheap Android phones are the sole computing device.
- Nokia threat reports (as summarized in the thread) are cited: most Android malware comes from trojanized apps distributed outside major stores.
- Others argue:
- Users have always installed software “from anywhere” on traditional computers; app‑store lockdown is not the only path to safety.
- Play Store itself hosts malicious apps, and Google policies often block privacy‑enhancing tools more than harmful ones.
Google Play Signing Keys and Control
- Some are more alarmed by Google’s app‑signing policies than by scare screens.
- Concern: requiring developers to hand over signing keys lets Google (or governments via Google) push modified updates, potentially subverting encryption or targeting specific users.
- Discussion touches on F-Droid’s reproducible builds, separate keys, and the evolving ability to share upstream signatures, with new risks if Google also holds those keys.
Why Google “Loses” and Apple Doesn’t (Yet)
- Multiple comments stress antitrust hinges on market definition and timing:
- For Google, “Android app distribution” is treated as a market they later tightened after gaining dominance.
- For Apple, there is argued to be no separate “iOS app distribution” market; iOS is a closed platform from day one with stable rules.
- Google’s internal communications (e.g., moving sensitive chats to short‑retention channels) reportedly hurt them in court.
- Some expect future regulation (especially from the EU) to eventually force Apple to open up similarly.
Courts vs Legislatures and Systemic Issues
- Several argue inconsistent outcomes stem from outdated laws being stretched to new platform models.
- There is frustration that Congress has not defined clear app‑store rules, leaving judges and settlements to improvise.
- Side debates examine corporate personhood, lobbying as “free speech,” and limited executive liability, framed as structural reasons big tech repeatedly escapes meaningful punishment.