Apple is finally bringing RCS messaging to the iPhone

Original Article ↗ Hacker News Discussion ↗

Apple’s plan to add RCS support to iOS 18 is seen as a modest technical upgrade over SMS—better media quality, typing indicators, Wi‑Fi support—but many point out that standard RCS still lacks end‑to‑end encryption and largely routes through Google-operated infrastructure in practice. Commenters debate whether this change reduces Apple’s iMessage lock‑in or simply swaps one closed ecosystem problem for another, given Google’s proprietary E2EE extension and history of fragmented messaging products. The thread also contrasts US reliance on carrier-based texting with Europe’s near-universal use of apps like WhatsApp, and raises regulatory angles around interoperability, security, and accessibility.

RCS and Encryption

  • RCS by default is not end-to-end encrypted; it typically offers only TLS in transit.
  • Google’s Messages app adds E2EE via a proprietary extension using the Signal protocol, but:
    • It only works when both sides use Google Messages.
    • It depends on Google-run key servers and isn’t available to other RCS clients (including Apple).
  • Several commenters see this as a PR win for Google that blurs the difference between “RCS” and “Google’s E2EE RCS.”
  • Some hope RCS could gain standardized E2EE in the GSMA “Universal Profile,” but note it isn’t there today.

Apple’s Motives and Lock-In

  • Many view Apple’s RCS move as minimal, “malicious compliance”: green bubbles remain, and iMessage still has more features and E2EE.
  • Some argue Apple is preempting regulators (EU, US, China) on interoperability; others note EU explicitly kept iMessage out of DMA scope.
  • iMessage is criticized as a lock-in tool (problems when switching away, deregistration issues, social pressure around blue bubbles).

Google’s Role and Messaging History

  • RCS infrastructure is often run by Google via Jibe because carriers don’t want to operate their own servers.
  • Several commenters distrust Google’s role: centralization, plaintext visibility for non-E2EE RCS, and dependence on a company with a long history of starting and killing messaging products (GTalk, Hangouts, Allo, Duo, etc.).
  • Opinions split on Google Messages: some find it fine; others think “nobody uses it” or recall past failed integrations with SMS.

Green vs Blue Bubbles and Accessibility

  • Green still indicates non‑iMessage traffic (SMS/RCS), which:
    • Signals lack of iMessage features and often no E2EE.
    • In group chats can degrade media quality and reliability.
  • Debate over whether bubble colors are primarily:
    • A UX signal about protocol/encryption/feature set.
    • A social marker that stigmatizes non‑iPhone users.
  • Multiple comments criticize Apple’s color contrast (white text on bright green/blue) as failing accessibility guidelines; others counter that iOS has system-wide accessibility settings to increase contrast.

RCS vs SMS/MMS and Global Context

  • RCS is seen as an improvement over SMS/MMS (better media, IP-based, can work over Wi‑Fi), but:
    • Still tied to phone numbers and carriers.
    • Considered outdated or irrelevant in regions where WhatsApp/Signal/Telegram dominate.
  • Mixed views on regulators:
    • Some fear RCS as a surveillance-friendly, cleartext baseline.
    • Others note that in practice, in many places, people already rely on OTT encrypted apps instead of SMS/RCS.