admin The return matters because RCS has already improved cross-platform messaging by replacing older SMS and MMS functions with higher-resolution media sharing, typing indicators and read receipts. What it has lacked on iPhone-to-Android conversations is the same end-to-end protection long associated with iMessage and, in a more limited way, with Google Messages on Android. Apple’s latest beta suggests the company is moving from pledge to implementation, though not yet to full public deployment.
Apple’s own release documentation for iOS 26.4 said RCS end-to-end encryption would be available for testing between Apple and Android devices, but also made clear that the feature would not ship in that release. By contrast, iOS 26.5 beta surfaced with Apple’s developer release listings on 30 March 2026, and outside testing reports say the Messages settings again show an “End-to-End Encryption ” option under RCS Messaging, switched on by default. Those reports also note that Apple’s latest release notes do not carry the same explicit warning that the feature will be held back from the final version.
That change in wording is important, but it does not amount to a guarantee. Apple has a history of testing features in beta software and altering rollout plans before public release. The label itself points to a staged introduction, and reports indicate encrypted RCS conversations will only work where device, software and carrier conditions align. For consumers, that means the headline privacy improvement may arrive unevenly at first, even if Apple keeps it in the shipping build of iOS 26.5.
The broader industry backdrop helps explain why Apple is moving now. In March 2025, the GSMA announced new RCS specifications that add end-to-end encryption based on Messaging Layer Security, or MLS, describing it as a major step towards secure and interoperable messaging. Apple said at the time it had helped drive the cross-industry effort and would add support for encrypted RCS messages to iOS, iPadOS, macOS and watchOS in future software updates. That commitment framed encryption not as an optional add-on but as part of a standards-based overhaul of cross-platform messaging.
For years, Google Messages users on Android have had end-to-end encryption in qualifying RCS conversations, but only when all participants use Google Messages with RCS enabled. That left cross-platform texting in an awkward middle ground: richer than SMS, but weaker on privacy than many users assumed. Security advocates have long argued that this gap matters because transport-level protection is not the same as end-to-end encryption, which prevents intermediaries from reading message content while it is in transit. Apple’s latest beta appears to be an attempt to bring iPhone participation into the stronger model envisioned by the GSMA’s updated standard.
The commercial and regulatory stakes are also larger than a single settings toggle. Apple’s decision in 2023 to adopt RCS was widely seen as a response to mounting pressure over messaging interoperability, especially as regulators in Europe examined how dominant platforms handle switching costs and cross-platform communication. Since then, Apple has tried to improve the experience without surrendering the security branding that has long distinguished iMessage. Encrypted RCS gives Apple a way to argue that interoperability and privacy do not have to be mutually exclusive.
Even so, there are limits to how transformative this beta should be treated at this stage. End-to-end encryption for RCS will not erase the differences between iMessage and Android messaging ecosystems, and Apple has not yet publicly declared a final launch date for broad consumer availability. Nor is every RCS feature advancing at the same pace. The GSMA’s newest Universal Profile 4.0 work points to richer tools such as messaging-initiated video calling, showing that the standard is still evolving while Apple and Google decide which elements to support and when.
