Nearly a year after the GSM Association standardized end-to-end encryption for RCS, Apple is finally showing signs of implementation in iOS 26.3 Beta 2, bringing secure messaging to Android-iPhone conversations.
The long wait for encrypted cross-platform messaging may finally be ending. Signs of end-to-end encryption support for RCS messages have appeared in iOS 26.3 Beta 2, nearly a year after the GSM Association published the RCS Universal Profile 3.0 standard.
What Changed in the Standard
When Apple adopted RCS in iOS 18, it notably skipped the encryption features that Google had been pushing through its proprietary implementation. That made sense from a standards perspective—Apple typically avoids adopting vendor-specific extensions. The GSM Association's Universal Profile 3.0 changed the equation by creating an industry-wide E2EE specification that everyone could support.
The encryption protects more than just text. Files, photos, videos, and group chats all get the same protection. This puts RCS on par with iMessage and WhatsApp for privacy, but with the crucial advantage of working across platforms.
What's Visible in the Beta
The discovery in iOS 26.3 Beta 2 isn't the encryption itself, but rather the user interface elements that will manage it. Apple has added settings that will show encryption status to users and allow them to control encryption preferences. This suggests the underlying implementation is either complete or close enough that the UI work has begun.
The beta code reveals Apple's approach to making encryption transparent. Users will be able to verify their conversations are protected and adjust settings as needed. This level of user control matches how Apple handles encryption in iMessage, where users can see at a glance whether a conversation is secure.
Timeline Uncertainty
Apple hasn't announced when encrypted RCS will reach the public. The feature could arrive with the stable release of iOS 26.3, or it might be held back for iOS 27. The company's silence on the matter suggests they're still finalizing the implementation.
Beyond Encryption: Universal Profile 3.0 Features
Encryption isn't the only improvement in the standard. Universal Profile 3.0 brings several features that make RCS more competitive:
- Inline replies: Reply directly to specific messages in a conversation
- Message editing: Fix mistakes after sending (within a time window)
- Unsend capability: Take back messages you didn't mean to send
- Proper Tapback support: Emoji reactions that work consistently instead of the current workaround
These features bring RCS closer to the messaging experience users expect from modern apps.
The Road Ahead
The GSM Association has already moved on to Universal Profile 3.1, which adds support for xHE-AAC audio codec, spam reporting, improved file transfer security, and better performance on unstable connections. This shows the standard is evolving quickly, which raises questions about how Apple will keep pace.
For now, the key development is that Apple appears committed to implementing the encryption standard. When it arrives, Android and iPhone users will finally be able to message each other with the same privacy protections they get within their own ecosystems. That's a significant step toward breaking down the walls between platforms.
The implementation details matter. Apple's history suggests they'll want to verify the encryption implementation thoroughly before releasing it. That could explain the delay between the standard's publication and the feature's arrival. If the beta UI elements are any indication, though, the wait might be nearly over.
Comments
Please log in or register to join the discussion