How WhatsApp for business changed the world

Privacy and Security Concerns

  • Several commenters dispute claims that privacy is “in the DNA” of WhatsApp, pointing out that:
    • Group and community chats expose all participants’ phone numbers to each other.
    • Random spam group invites can both disclose numbers and push scams.
  • Some criticize the app’s permission model:
    • Pressure to grant full contact access and persistent location permission.
    • Reports that after some updates it stopped working without full contacts access.
  • Comparisons:
    • Telegram is criticized for not using end‑to‑end encryption by default.
    • Signal is praised for privacy but some dislike added “stories” / status features.
    • Viber is mentioned as more spam‑resistant because it doesn’t allow VoIP numbers.

Spam, Business Messaging, and Controls

  • WhatsApp Business is blamed for a rise in spam and scam messages from rotating numbers.
  • Blocking and reporting are perceived as ineffective.
  • There is a “block unknown account messages” setting, but:
    • It only auto‑blocks after “high volume” traffic, whose threshold is opaque.
    • Some see this “opt‑out with hidden thresholds” design as hostile to users.
  • Others note they’ve used WhatsApp for many years with virtually no spam, suggesting regional and legal differences (e.g., stricter EU ad rules).

Product Evolution and Enshittification Debate

  • Post‑acquisition changes draw mixed reactions:
    • Criticisms: more bugs, clunkiness, “communities,” channels, business features, disappearing local backups, and heavy media compression.
    • Some see WhatsApp following WeChat’s path and call it “enshittification.”
  • Defenses:
    • Strong adoption of “stories/status,” especially outside the US.
    • Appreciated additions: better desktop app, dark mode, multi‑device, payments, profile QR codes, Meta AI integration.
    • Meta AI is described by some as genuinely useful for quick research and coding help.

Why WhatsApp Is Ubiquitous (Outside the US)

  • Common explanations:
    • Historically expensive or limited SMS and especially international SMS/roaming, versus cheaper data.
    • Need for cross‑platform messaging where iMessage isn’t dominant.
    • Early availability on a wide range of devices (Symbian, older Nokias, BlackBerry), with a small one‑time fee.
  • In the US, unlimited domestic SMS, iMessage, and Facebook Messenger reduced pressure to adopt WhatsApp; RCS is starting to appear but has reliability and feature gaps.

Using WhatsApp for Business and Customer Service

  • Positive experiences:
    • Hotels, restaurants, and service providers use WhatsApp for async support, orders, and avoiding roaming charges.
    • Some find it more convenient than calls or email, treating it like normal chat.
  • Negative experiences:
    • Professionals pushing confidential information over WhatsApp instead of email, with poor organization and shorthand replies.
    • Criticism that businesses rely on a proprietary app instead of open standards (SMS, email, web forms), effectively forcing customers into specific ecosystems.

Architecture and Technical Questions

  • One explanation describes WhatsApp as:
    • Using the phone as the primary message store, with servers mainly relaying and holding messages only until delivery.
    • Web/desktop acting as thin clients syncing from the phone (though newer multi‑device support reduces strict phone dependence).
  • Some see the web/desktop client as lazy Electron‑style UX; others note newer native-ish macOS apps feel faster.
  • Questions are raised (but not resolved) about:
    • How language statistics are computed if messages are truly end‑to‑end encrypted.
    • How WhatsApp builds large‑scale business features on top of the Signal protocol and what compromises that entails.