Platform Tilt

Original Article ↗ Hacker News Discussion ↗

Mozilla’s new “Platform Tilt” site prompts debate over how Apple, Google, and Microsoft use OS- and app-level controls to favor their own browsers and services, from default search behavior to limitations on third‑party engines and extensions. Commenters weigh the benefits of tighter mobile sandboxing and privacy against the drawbacks for browser interoperability, data portability, and features like ad blocking. Many argue that antitrust action and clearer platform rules are needed, while others note that user apathy, UX trade‑offs, and performance gaps also limit alternatives like Firefox.

Browser data access & migration

  • Disagreement over Mozilla’s complaint that Android blocks third‑party access to browsing history, bookmarks, and cookies.
  • Some see such access as an obvious privacy risk and prefer explicit export flows (e.g., OS‑mediated archives, share‑sheet‑based transfers, or new permissions/content providers).
  • Others argue controlled, user‑approved access is fine and essential for easy browser switching, especially for bookmarks.
  • Several note Firefox for Android itself still lacks good bookmark export/import, weakening Mozilla’s position.

Apple/iOS restrictions & Safari’s role

  • Many criticize iOS rules: WebKit-only engines, limited extensions, and content blockers that effectively work only in Safari, harming Firefox’s competitiveness.
  • Some worry Mozilla’s proposal for better Messages integration (e.g., accessing message data) is too privacy‑invasive; they’d prefer narrower “recent links” APIs.
  • Debate over whether Safari’s de‑facto monopoly on iOS is a “lesser evil” that slows full Chrome dominance or just another harmful monopoly that also suppresses Firefox.
  • There’s interest and skepticism about whether Apple would ever allow JIT for third‑party engines even if the EU forces engine choice.

Chrome dominance, antitrust & Mozilla’s strategy

  • Several argue that technical superiority alone won’t move Firefox’s market share; defaults and anti‑competitive tying (search, YouTube prompts, etc.) dominate behavior.
  • Strong view that real change depends on antitrust, including curbing self‑preferencing (e.g., Chrome prompts) and possibly mandating cross‑browser compatibility testing.
  • Some see Mozilla as too Google‑dependent; others counter that Mozilla has meaningfully improved Firefox and is constrained by structural market issues, not just leadership.

Embedded webviews & user experience

  • Many complain about apps opening links in embedded webviews or custom tabs to retain engagement, which:
    • Enables extra tracking.
    • Bypasses browser sync for passwords, history, bookmarks.
    • Confuses less technical users who struggle with app switching.
  • Proposed remedies: force third‑party links into the default browser; restrict “non‑browser” apps to a short, declared domain whitelist; or improve OS‑level “custom tab” behavior and controls.

Firefox quality & platform quirks

  • Some Android users avoid Firefox due to perceived slowness, layout shifts, keyboard and shortcut issues, and occasional hangs/crashes.
  • Others report no such problems and praise recent feature work (extensions on Android, privacy tools), but concede Firefox can feel rough in places.
  • Additional tilt examples: macOS and Windows sometimes ignoring default browser settings (e.g., Mail search opening Safari, Windows Search forcing Edge/Bing), Google Colab copy/paste working better in Chrome, and corporate VPNs only supporting certain browsers.