For years, there has been a quiet gap in mobile security.
If you sent a message from iPhone to iPhone, it was encrypted. If you used apps like WhatsApp or Signal, it was encrypted.
If you texted someone on Android from an iPhone, it usually was not.
That gap is now closing with iOS 26.5, in which Apple is introducing end-to-end encryption for RCS messaging between iPhone and Android devices. This brings cross-platform messaging closer to the same security standard users already expect within Apple’s ecosystem.
On the surface it’s a much-needed messaging upgrade, and it also it represents a significant shift in how Apple approaches interoperability, privacy and platform boundaries.
What is actually changing
RCS, or Rich Communication Services, has been positioned as the modern replacement for SMS. It supports read receipts, typing indicators, media sharing and group messaging.
Apple added RCS support to iPhone relatively recently, but with a major limitation. Messages between iPhone and Android users were only protected by transport-level encryption, meaning they were secure in transit but could still be accessed by intermediaries or servers.
That is very different from end-to-end encryption (E2EE), where only the sender and recipient can read the message content.
With iOS 26.5, that changes. RCS conversations between iPhone and Android devices can now be fully end-to-end encrypted, provided both devices and carriers support the latest RCS standard.
Encrypted conversations are marked clearly in the interface, typically with a lock icon, and the feature is enabled by default where supported.
Why did it take so long?
Apple’s reluctance to embrace RCS has been well documented. And in truth, it’s understandable on Apple’s part – iMessage already provided a secure, feature-rich experience within Apple’s ecosystem. Supporting RCS, especially without encryption, would have meant accepting a weaker standard for cross-platform messaging.
Historically, that gap worked in Apple’s favour. The contrast between iMessage and SMS created a clear differentiation between iPhone and Android users.
On the other side, standard RCS did not include universal end-to-end encryption, which meant Apple would have been supporting a protocol that did not meet its own privacy baseline. That has now changed, largely due to updates in the GSMA’s RCS Universal Profile, which introduced a standardised approach to encrypted messaging. For a long time, cross-platform messaging meant compromise. Either you stayed within a closed ecosystem and kept full functionality, or you stepped outside it and accepted limitations.
Once encryption became part of the standard, Apple’s position shifted. Beyond the technical change, this signals something more interesting: Apple is moving towards stronger interoperability without compromising its security model.
It also allows Apple to support a shared standard while maintaining its privacy positioning.
That is likely to become more important over time, particularly as regulatory pressure around platform openness continues to increase.
Why this matters more than it looks
At a technical level, this closes one of the more obvious gaps in mobile communication security.
For years, a simple behaviour created a risk: an employee messaging a colleague on a different platform would drop from encrypted communication to a less secure channel without realising it. And employees frequently communicate across platforms. Contractors, clients and partners are not always on the same device ecosystem. Messaging often becomes an informal extension of business communication.
Encrypted RCS helps close that gap, though note that it does not replace the need for secure collaboration tools or formal communication platforms. It does, however, improve the baseline level of protection for everyday interactions.
From a security perspective, it removes a weak point that has existed for over a decade.
The catch: it will not be instant
There is an important caveat.
RCS is not controlled solely by Apple or Google. It depends heavily on carrier support and network infrastructure.
That means:
- Not all users will see encrypted RCS immediately
- Availability will vary by region and network
- Some conversations will still fall back to non-encrypted messaging
Apple has already indicated that the rollout will be gradual and that support depends on both sender and recipient meeting the required conditions. This creates a transitional period where messaging security may still be inconsistent across different users and organisations.
A Dr Logic perspective
The introduction of end-to-end encrypted RCS is a meaningful step forward for mobile security. It removes a long-standing inconsistency in how messages are protected across platforms and brings everyday communication closer to a consistent security standard.
As noted, the rollout will take time and not every environment will support it immediately. Even so, the direction is clear: cross-platform communication is becoming more secure by default.
For organisations managing Apple devices, this reinforces a broader point: security is no longer limited to infrastructure and applications. It extends into the everyday behaviours of users and the tools they rely on.
Ensuring those tools operate within a secure framework remains a critical part of modern IT strategy.
If your organisation is reviewing how mobile communication fits into its wider security posture, Dr Logic can help ensure your Apple environment remains aligned, secure and ready for what comes next.
