Perhaps the best thing to happen to smartphones in the past five years was Apple’s decision to start supporting RCS. Ever since, texting between iPhone and Android hasn’t been a nightmare caused by SMS: Group chats function as they should, photos and videos can be sent in high quality, and you can even see when the other person is typing—though the messages are still green.
While the experience is miles better than it used to be, it isn’t perfect. There are still some key functions missing from RCS on iPhone. For instance, you can’t unsend messages, reply to a thread, or edit iPhone messages. The latter can only happen on the Android side, while only iPhones can react with emojis right now. The biggest omission, however, is support for end-to-end encryption (E2EE). This is arguably the most important advantage RCS has over SMS. E2EE “scrambles” your messages, and only you and the recipient(s) have the “keys” to unscramble them. If a hacker were to remotely access your messages from an untrusted device, they wouldn’t be able to read them: The only way to see these messages in plain text is to have access to the trusted device associated with them.
If you have an Android device, and you text with other Android devices using Google Messages, you likely have this advantage. You may see a small lock icon next to your messages as you send them, indicating that texts are sent with E2EE. iPhones have this advantage when texting other iPhones, as iMessage is E2EE as well. But when you text from an iPhone to an Android, whether or not you’re using RCS or SMS, those messages are not protected by encryption, which leaves you vulnerable to hacking.
End-to-end encryption support for RCS is live in the iOS 26.4 beta
That’s now changing. Apple is currently testing E2EE support for RCS on iPhone. Not only that, anyone can try it out right now—assuming you’re fine taking on the risks of beta software.
The change comes with the second beta for iOS 26.4, which Apple released on Monday. Apple’s first beta for 26.4 added an initial layer of support, but only for iPhones texting each other with iMessage disabled. The second beta now supports E2EE for RCS communications with Android devices. As long as your Android friends are running the latest version of Google Messages, and you’re running the second iOS 26.4 beta, you can rest easy knowing your messages are protected by end-to-end encryption.
What do you think so far?
However, this doesn’t mean that those of us waiting for the official iOS 26.4 release will enjoy the same. While beta features are always subject to change, Apple explicitly says in its release notes that, “This feature is not shipping in this release and will be available to customers in future iOS, iPadOS, macOS, and watchOS 26 releases.” It seems the company is getting a jump on testing in anticipation of a future iOS 26.4.1, iOS 26.5, or maybe even an iOS 27 release.
Don’t install the iOS 26.4 beta without knowing the risks
You’ll need to install the latest beta on your iPhone to give this encryption a try—but don’t do that without thinking it through. Beta software is in testing, which means there may be bugs and other instabilities you aren’t used to dealing with in iOS. If something goes wrong, and you need to uninstall the beta, you’ll need to reset your iPhone entirely. Unless you have a full backup of iOS 26.3 on your computer, you could lose data. As such, I never recommend installing betas on your primary device. It’s your choice, of course: Just understand the risks.
If you do decide to try the beta, you’ll also have access to other new features in iOS 26.4—namely, a new Apple Music experience with an AI playlist generator, fresh design, and the ability to add songs to multiple playlists at once.
