Apple to Add End-to-End Encryption for RCS in iOS 26.5 Ahead of WWDC: why it matters for developers

Apple plans a mid-cycle iOS release, version 26.5, that will enable end-to-end encryption for Rich Communication Services (RCS) messages sent between iPhones and Android devices. The change brings cross — platform text conversations closer to the privacy guarantees iMessage users already have within Apple’s ecosystem, and is slated to arrive before the company’s Worldwide Developers Conference (WWDC), which is about one month away. This update matters because it replaces previously unencrypted cross — platform messages with encrypted RCS flows, altering the security baseline for millions of users who message across platforms.

RCS support first appeared on iPhone with iOS 18, where Apple added richer cross — platform features such as read receipts and typing indicators. Until iOS 26.5, however, Apple’s RCS implementation did not adopt the protocol’s end-to-end encryption capability, so texts between iPhones and Android phones remained effectively less private than iMessage conversations between Apple devices. For years the default path for messages between iPhones and Android phones fell back to SMS, a legacy protocol that lacks modern features including end-to-end encryption, which left a notable privacy gap for cross — platform messaging.

Enabling RCS end-to-end encryption in iOS 26.5 therefore represents a shift in Apple’s approach to interoperability for standard text conversations. With the update, iPhone — to-Android exchanges that use RCS will gain the same basic privacy guarantees that iMessage provides within Apple’s ecosystem, provided both ends of a conversation support encrypted RCS sessions. This narrows a longstanding disparity in how private conversations can be when participants are on different platforms, improving user privacy without changing how iMessage operates for Apple — only conversations.

The change has practical implications for builders and engineers who integrate or rely on carrier messaging and cross — platform communication. Apps, services, and back-end systems that handle, route, or audit user messages should prepare to encounter RCS-encrypted traffic where plaintext SMS previously existed. Teams should verify how feature parity — read receipts, typing indicators and other RCS features — behaves under encrypted sessions and update logging, monitoring, and compliance practices to avoid treating encrypted content as accessible plaintext.

Timing and rollout details matter for developers and operators. Apple intends to ship iOS 26.5 ahead of WWDC, while iOS 27 is expected to be the major next-generation release showcased at that event. Operators, carriers, and Android vendors should monitor iOS 26.5 rollout notes and testing tracks to observe how carriers and Android clients interoperate with Apple’s encrypted RCS implementation once it becomes broadly available, and to assess any carrier — level or cross — client interoperability issues that may arise.