U.S. moves closer to filing antitrust case against Apple

Original Article ↗ Hacker News Discussion ↗

U.S. antitrust authorities are reportedly preparing a case against Apple that probes how tightly its hardware, software, and services are tied together, from iMessage lock-in and Apple Watch exclusivity to App Store rules and browser-engine restrictions on iOS. Commenters debate whether existing antitrust law actually forbids Apple’s self-preferencing and “walled garden” approach or whether new legislation, like the EU’s DMA, is needed to address modern digital ecosystems. Many see Apple’s practices as harmful to competition and interoperability—especially around messaging, payments, and app distribution—while others argue consumers can always choose Android and that vertical integration is a legitimate competitive strategy.

Antitrust legal framing

  • Several commenters argue current U.S. antitrust law mainly forbids “worsening” competitors’ access or coercing third parties, not simple self‑preferencing; they see Apple’s behavior as likely legal unless courts or Congress expand doctrine.
  • Others emphasize statutory law is broad and under-interpreted for modern digital platforms, so courts have latitude to treat Apple’s conduct as illegal, especially given its size and ecosystem power.
  • The Microsoft IE case is heavily debated: some say Apple’s situation is different (no OEM coercion, integrated hardware+OS), others say effects on competition and defaults are analogous or worse.
  • Some expect DOJ to “push the envelope” to test how far existing law can go; others think that belongs to legislators, pointing to EU’s DMA/GDPR as better models.

Messaging and iMessage lock‑in

  • Many U.S. users report real social exclusion and degraded UX for Android users (green bubbles, low‑res MMS, broken group chats), seeing iMessage as a deliberate lock‑in tool and “embrace, extend, extinguish” of SMS.
  • Counterpoint: Apple runs an expensive service and has no duty to provide it cross‑platform or to third‑party clients; refusal to deal is framed as legitimate competition, not antitrust.
  • There is debate over reverse‑engineered clients like Beeper Mini: some see them as legitimate “adversarial interoperability,” others as freeloading on Apple’s infrastructure.
  • Some propose legal thresholds where network‑effect services above a market share must interoperate; others fear that mandated “interoperability” could freeze protocol innovation and weaken end‑to‑end encryption.

App Store, browsers, and developer constraints

  • Strong criticism of Apple/Google’s 30% cut, anti‑steering rules, and banning alternative app stores or browser engines on iOS; described as a de facto tax and both monopoly and monopsony over iOS apps.
  • Others note 30% is common in retail and game stores (e.g., Steam), and argue it funds OS and tools development; Epic’s 12% store is cited both as evidence lower fees are possible and as a business that still loses money.
  • Requiring Xcode on a Mac to build/upload iOS apps is viewed by some as tying software markets to Mac hardware; others say porting the toolchain would be costly and increase low‑effort shovelware.

Ecosystem lock‑in: hardware and services

  • Apple Watch’s iPhone‑only pairing, AirTags’ leverage of the iOS install base, NFC/payment restrictions, and WebKit‑only browsers are seen as ecosystem lock‑in that competitors can’t realistically match.
  • Defenders answer that consumers choose between Android and iOS, that vertical integration yields better UX and security, and that Apple has no obligation to support rival devices or engines.

Security, privacy, and government motives

  • Some suspect antitrust pressure is partly a pretext to weaken Apple’s encryption and security barriers for surveillance access; others counter that many cross‑platform encrypted messengers exist, and lock‑in does not equal better security.
  • There is tension between those who want root‑level control/sideloading as a user right and those who prioritize Apple’s curated, locked‑down model for safety.

Desired remedies

  • Proposed remedies range from:
    • breaking up Apple or banning exclusive app stores,
    • mandating competing app stores and browser engines on iOS,
    • requiring protocol or service interoperability once market share/network‑effect thresholds are passed,
    • to more modest, targeted rules (anti‑steering, payments, sideloading) modeled on the EU.
  • Skeptics of breakup argue it might just create coordinated cartels of smaller firms and prefer precise, practice‑focused regulation.