Bold headline: Apple tests true privacy for cross‑platform chats by bringing end-to-end encryption to Apple‑to‑Android RCS. And this is the part most people miss: it’s a staged rollout that hinges on device, carrier, and software readiness.
Here’s the gist in plain language: Apple began testing end‑to‑end encryption (E2EE) for RCS messages exchanged between Apple devices and Android devices. This follows its September 2024 rollout of RCS on iOS 18, after which Apple promised that cross‑platform RCS chats would eventually be fully encrypted. Now, roughly a year and a half later, Apple is putting that promise into a hands‑on test in iOS 26.4 Developer Beta 2.
What’s new and why it matters:
- The encryption backbone: Apple’s test uses the GSMA’s RCS Universal Profile 3.0, which relies on Messaging Layer Security (MLS) to bridge the security gap between different device ecosystems. In other words, MLS helps keep messages private even when they travel between iPhone and Android clients.
- Current encryption landscape: Apple‑to‑Apple messages are already encrypted (using PQ3), and Android‑to‑Android messages rely on the Signal protocol. The new test aims to extend strong end‑to‑end protection to cross‑platform conversations.
- Beta notes from Apple: In the iOS 26.4 Developer Beta 2 release notes, Apple states that E2EE will be testable between Apple and Android devices in this beta. It is not shipping in this release and will be available in future iOS, iPadOS, macOS, and watchOS updates. The encryption is in beta, not universal, and not all devices or carriers will support it at first. Encrypted conversations will be clearly labeled, and their messages should remain unread while in transit between devices.
- Practical access for testers: If you’re using the latest developer beta, you can enable E2EE testing by going to Settings > Messages > RCS Messaging and turning on End-to-End Encryption (Beta). Android users will need to be enrolled in the Google Messages app beta to participate in the handshake with Apple’s encryption protocol.
Context and implications:
- A step toward truly interoperable privacy: This initiative aims to close the security gap that exists when iOS and Android users chat via RCS. By adopting MLS‑based end‑to‑end protection, Apple and Google are moving toward a more private cross‑platform messaging experience.
- Limits and caveats: As noted by Apple, this feature is beta, not available to every device or carrier yet, and relies on future software releases. Early adoption will likely be limited to specific configurations and regions before a broad rollout.
Controversy and opportunities for discussion:
- Should cross‑platform privacy warrants require uniform carrier support, or is staged rollout with gradual expansion preferable to ensure reliability? What risks exist if encryption is not uniformly supported across all devices or networks?
- Do you expect any trade‑offs between privacy and features (like message read receipts or backup behavior) during this cross‑platform E2EE testing phase? Share your thoughts in the comments.
