Your text messages are about to get a major security upgrade—but it’s not without its controversies. Google and Apple have officially begun testing end-to-end encrypted RCS messaging between Android and iOS devices, marking a significant leap in cross-platform privacy. But here’s where it gets interesting: while this move promises to make conversations unreadable to anyone but the sender and receiver, it also raises questions about accessibility and potential misuse. Let’s dive in.
As part of the RCS Universal Profile from the GSMA, this encryption ensures that messages sent between Android and iOS users remain private, even as they travel between devices. For iOS users, the Messages app will now display green bubbles with a new label: “Text Message · RCS | [lock icon] Encrypted” at the center of the screen. Android users on Google Messages will see the same lock icon, just like they do for messages sent to other Android devices. Sounds straightforward, right? But this is the part most people miss: Apple’s adoption of RCS in iOS 18 last September was already a big deal, enabling features like typing indicators, read receipts, and higher-quality media sharing with Android users. Now, with end-to-end encryption in the mix, the stakes are even higher.
To test this feature, iPhone users need to be running iOS 26.4 beta 2, available on supported carriers. After installing, head to Settings > Messages > RCS Messaging and ensure “End-to-End Encryption (Beta)” is enabled—it’s on by default. Android users, meanwhile, must be on the latest Google Messages beta (you can join the testing program here). But here’s the catch: as with any beta, there could be message delivery issues, service interruptions, or unexpected bugs. So, while this is a step forward, it’s not without its growing pains.
And this is where it gets controversial: should end-to-end encryption be the default for all RCS messages, or should users have the option to disable it? Some argue that default encryption prioritizes privacy, while others worry it could complicate troubleshooting or exclude users who prefer simplicity. Apple has already stated that end-to-end encrypted RCS will be enabled by default in a future iOS 26 update, but the debate is far from over. What do you think? Is this a win for privacy, or does it introduce unnecessary complexity? Let us know in the comments.
FTC Disclosure: We use income-earning auto affiliate links. Learn more.
