Encryption protection that iMessage users have long enjoyed
For years, the boundary between iPhone and Android has been more than aesthetic — it has been a security gap, leaving cross-platform messages exposed in transit. With iOS 26.5 entering its final testing phase, Apple is closing that gap by extending end-to-end encryption to RCS messages, the modern successor to SMS. The move acknowledges that true communication security cannot stop at the edge of a single ecosystem, and signals a broader reckoning with the responsibilities that come with owning the dominant platforms of daily human connection.
- Every RCS message sent between an iPhone and an Android device has traveled unencrypted — a quiet vulnerability affecting millions of daily conversations.
- Apple's iOS 26.5 Release Candidates are now in developers' hands across all six operating systems, signaling a public launch is imminent.
- The headline feature — end-to-end encryption for cross-platform RCS messaging — directly addresses a long-standing security blind spot that neither Apple nor Google had fully resolved together.
- Regulatory and competitive pressure around messaging security has been mounting, and this move removes one of the last technical objections to RCS as a universal standard.
- Battery and inter-device communication improvements round out the update, with the full public rollout expected within weeks.
Apple has moved iOS 26.5 into its Release Candidate phase, pushing final pre-release versions across iPadOS, macOS, watchOS, tvOS, and visionOS simultaneously — a sign that a public launch is close.
The defining feature of this update is end-to-end encryption for RCS messages exchanged between iPhones and Android devices. RCS, the modern replacement for SMS, already supports richer features like read receipts and high-quality media, but cross-platform messages have until now traveled without encryption — leaving them vulnerable to interception. Apple's own iMessage has long offered encryption, but only between Apple devices. When conversations crossed into Android territory, that protection disappeared.
With iOS 26.5, that changes. Encryption will apply to all RCS messages flowing between the two platforms, regardless of which side initiates the exchange. The timing is significant: Google has been championing RCS adoption for years, and Apple's embrace of encryption removes a key remaining objection to the standard.
The update also brings power management refinements and improvements to how Apple's devices communicate within its ecosystem — welcome news for Apple Watch and Vision Pro users who have long scrutinized battery performance.
Developers are now testing these Release Candidates for bugs and compatibility issues. If history holds, the public rollout will follow within weeks, bringing more secure cross-platform messaging to the many users who regularly communicate across the iOS-Android divide.
Apple has moved its iOS 26.5 operating system into the final testing phase, releasing Release Candidates across its entire ecosystem of devices. The company simultaneously pushed out matching versions of iPadOS, macOS, watchOS, tvOS, and visionOS to developers, signaling that a public launch is imminent.
The centerpiece of this update is a security feature that has been conspicuously absent from smartphone messaging for years: end-to-end encryption for RCS messages sent between iPhones and Android devices. RCS, or Rich Communication Services, is the modern successor to SMS texting, offering features like read receipts, typing indicators, and higher-quality media sharing. Until now, when an iPhone user sent an RCS message to an Android phone, that message traveled unencrypted—a vulnerability that left cross-platform conversations exposed to interception.
Apple's move closes that gap. The encryption will apply to all RCS messages flowing between iOS and Android, regardless of which device initiates the conversation. This represents a significant shift in how the two dominant mobile platforms handle interoperability. For years, Apple has promoted its own iMessage service as the secure alternative, which uses end-to-end encryption by default. But iMessage only works between Apple devices. When an iPhone sends a message to Android, it falls back to standard SMS or, increasingly, RCS—and until now, without encryption.
The Release Candidate phase is the final testing ground before public release. Developers have access to these versions to identify bugs and compatibility issues. The fact that Apple is releasing RCs across all six of its operating systems suggests the company is confident in the stability of this update and expects to push it to the general public within weeks.
Beyond the encryption feature, the new versions include improvements to power management and the way Apple's devices communicate with one another. Battery efficiency gains are always welcome, particularly on devices like the Apple Watch and Vision Pro, which have historically faced scrutiny over battery life. The system communication enhancements suggest Apple is refining how its ecosystem of devices—phone, tablet, computer, watch, television interface, and spatial computing headset—coordinate with each other.
The timing of this release is notable. Cross-platform messaging security has become a competitive and regulatory pressure point. Google has been pushing RCS adoption as a replacement for SMS, and the addition of encryption by Apple removes one of the last technical objections to the standard. For users who regularly message across the iOS-Android divide, this update will mean their conversations gain the same encryption protection that iMessage users have long enjoyed within the Apple ecosystem.
With Release Candidates now in the hands of developers, the public rollout should follow within the coming weeks. The full scope of what iOS 26.5 will bring remains to be seen, but the RCS encryption feature alone represents a meaningful step toward more secure cross-platform communication.
The Hearth Conversation Another angle on the story
Why did it take Apple this long to encrypt RCS messages? Weren't they already encrypted on Android?
RCS itself didn't have encryption built in—it was designed as a carrier-level protocol, not an end-to-end encrypted service. Apple could have added encryption years ago, but they had little incentive. iMessage was their secure option, and it kept users locked into the ecosystem.
So this is Apple finally playing ball with Android users?
More like Apple recognizing that RCS is becoming the standard whether they like it or not. Google pushed it hard, carriers adopted it, and now encryption is table stakes. Apple's move makes RCS actually competitive with iMessage for security.
What about the other improvements mentioned—battery life, system communication?
Those are the quiet wins. When six operating systems ship at once, it usually means Apple found something that benefits the whole ecosystem. Better battery on a Watch or Vision Pro matters more to most people than encryption they'll never see working.
Does this mean iPhone and Android users will finally have parity in messaging?
For encryption, yes. But iMessage still has features RCS doesn't, and it still only works between Apple devices. This closes a security gap, but it doesn't merge the ecosystems. They're still separate.
When will regular people get this?
The Release Candidate phase is the last checkpoint. If no major bugs surface in the next few weeks, Apple will push it to everyone. We're probably looking at late May or early June.