Google has removed Conversations_im from the Play Store

Original Article ↗ Hacker News Discussion ↗

Google has abruptly removed the open‑source XMPP chat client Conversations from the Play Store, alleging it uploads users’ contact lists — a claim the developer and other XMPP maintainers strongly deny, saying contacts are only used locally. Commenters see the move as another example of opaque, bot-driven enforcement that hits smaller privacy‑friendly apps while large platforms that actually upload contacts remain untouched, with serious consequences for indie developers who rely on Play Store revenue. The incident feeds into broader worries about Android’s tightening controls, “security” used as a pretext for ecosystem lock‑in, and the need for alternative app distribution channels and regulatory oversight of dominant app stores.

Removal of Conversations_im and Contact Permissions

  • Google removed the XMPP client Conversations_im from Play Store, alleging it uploads users’ contacts.
  • Developer states contacts are only used locally (to match names/avatars) and not uploaded.
  • Other XMPP client maintainers report similar worries or incidents.
  • Some suspect the mere presence of the contacts permission plus an “insufficient” privacy policy text triggers automated removal.

Automated Enforcement, Appeals, and Lack of Support

  • Many commenters believe decisions are algorithmic, with little or no human review.
  • Experiences vary: some got rapid reversals after an appeal; others say they never reached a human.
  • One team claims Google only restored their app after they added a privacy-policy clause saying they upload contacts, even though they don’t.

Inconsistent Policy and Privacy/Security Theatre

  • Commenters note large apps (WhatsApp, TikTok, Facebook) clearly upload contacts yet remain in the store.
  • Several describe creepy contact-based suggestions, illustrating how social graphs are built even if one user refuses contact upload.
  • Many argue Google’s “security” posture mostly protects its own ad and platform interests, not users, and resembles PR or blame-shifting.

Impact on FOSS Developers and Distribution

  • Conversations is also on F-Droid, so technically still installable.
  • However, Play Store sales are said to fund near full‑time development; removal threatens that income.
  • Users discuss donating directly (e.g., via FOSS-friendly platforms) to compensate for lost Play revenue.

XMPP, Notifications, and Android Power Management

  • Several note XMPP clients often need contacts access and background connections.
  • Newer Android battery optimizations and OEM “app killing” make persistent connections unreliable without Firebase or foreground services.
  • Some say XMPP on Android is effectively dependent on push (Firebase or UnifiedPush) to be usable; others report Conversations worked better than most competitors for timely notifications.

Wider Critique of Android/Play and Alternatives

  • Developers complain about rising SDK requirements, complex compliance, Play Protect warnings, and feature removals that break existing apps (e.g., call blockers, automation tools).
  • Many describe this as “enshittification,” making Android more locked down and developer‑unfriendly.
  • Alternatives suggested: F-Droid, Aurora Store, custom ROMs (GrapheneOS, CalyxOS, LineageOS), de‑Googled phones, and rooting/unlocking bootloaders.

Regulatory and Structural Solutions

  • Some argue regulators should curb Google/Apple’s gatekeeper power, citing the EU Digital Markets Act and its fairness requirements.
  • Suggestions include separating OS vendors from app-store operators and creating nonprofits to fund legal challenges and enforce developer rights.