Apple Finally Makes Text Messaging Between IPhone and Android Secure.
Perhaps the best development for smartphones in the last five years was Apple’s decision to support RCS . Since then, messaging between iPhone and Android has ceased to be the SMS-induced nightmare: group chats work as expected, photos and videos can be sent in high quality, and you can even see when the other person is typing—though messages still appear in green.
While the user experience has improved significantly compared to the past, it’s not perfect. RCS on iPhone still lacks some key features . For example, you can’t unsend messages, reply to threads, or edit messages on iPhone. The latter is only possible on Android, and on iPhone, you can currently respond with emoji. However, the biggest drawback is the lack of end-to-end encryption (E2EE). This is perhaps the most important advantage of RCS over SMS. E2EE “encrypts” your messages, and only you and the recipient(s) have the “keys” to decrypt them. If a hacker gains remote access to your messages from an untrusted device, they won’t be able to read them: the only way to see these messages in plaintext is to have access to the trusted device associated with them.
If you have an Android device and exchange text messages with other Android devices via Google Messages, you likely have this benefit. You may see a small lock icon next to your messages when you send them, indicating that they are sent using end-to-end encryption (E2EE). iPhones also have this benefit when texting other iPhones, as iMessage uses E2EE. However, when you send text messages from iPhone to Android, whether you use RCS or SMS, these messages are not protected by encryption, making you vulnerable to hacking.
End-to-end encryption support for RCS is available in iOS 26.4 beta.
Things are changing . Apple is currently testing end-to-end encryption (E2EE) support for RCS on iPhone. Moreover, anyone can try it right now—as long as they’re willing to accept the risks associated with beta software.
The changes arrived with the second beta of iOS 26.4, which Apple released on Monday. The first beta of 26.4 added initial support, but only for iPhones exchanging text messages with iMessage disabled. The second beta now supports end-to-end encryption (E2EE) for RCS communication with Android devices. As long as your Android friends are using the latest version of Google Messages and you’re using the second beta of iOS 26.4, you can rest assured that your messages are protected with end-to-end encryption.
However, this doesn’t mean those of us waiting for the official release of iOS 26.4 will be able to enjoy the same experience. While beta features are always subject to change, Apple explicitly states in its release notes: “This feature is not included in this release and will be available to users in future releases of iOS, iPadOS, macOS, and watchOS 26.” It appears the company is beginning testing early, ahead of the upcoming releases of iOS 26.4.1, iOS 26.5, or perhaps even iOS 27.
Don’t install the iOS 26.4 beta without knowing the risks.
To try this encryption, you’ll need to install the latest beta on your iPhone—but don’t do this without careful consideration. The beta is still in testing, meaning it may contain bugs and other issues you’re not used to in iOS. If something goes wrong and you need to uninstall the beta, you’ll have to completely reset your iPhone. If you don’t have a full backup of iOS 26.3 on your computer , you could lose your data. Therefore, I never recommend installing betas on your primary device. Of course, it’s your choice; just understand the risks.
If you decide to try the beta, you’ll also have access to other new features in iOS 26.4, including a new Apple Music interface with an AI-powered playlist generator, a refreshed design, and the ability to add songs to multiple playlists at once.