- Draft messages are much easier to find in iOS 26
- The filtered code also suggests that iOS 26 will bring a great safety impulse
- Apparently, Apple is testing end -to -end encryption for RCS messages
How many times have you started writing a text message in iOS messages and then left it for later, just to forget who was messages and what was saying a few hours in the future?
It is a common fact, but iOS 26 includes a new feature that will make it very easier to find those unsteady texts, and it is almost shocking that Apple has not implemented it before.
If you are executing the Public Beta iOS 26, you can now filter your texts by draft. All you need to do is open the messages, touch the hamburger menu in the upper right corner, then select drafts under the filter by header. His entrance tray of his messages will now show only a draft of texts and nothing more, which will save him a lot of time taking advantage of all his existing threads in a vain attempt to find the elusive draft.
There are also filters for other situations. If you have scheduled messages for another moment, you will see a filter send later, for example, while there is a filter not read for any message you have not received to read.
Keep in mind that these filters only appear if there is a relevant message to filter. If you have no draft, for example, you will not see the draft filter. And these filters work independently of whether you are using the iPessage standard from iPhone to Apple iPhone or RCS/RCS/SMS messages sent to Android devices. Blue bubbles or green bubbles, it works.
Stronger security
Speaking of RCS messages, iOS 26 could include a significant safety impulse when it comes to sending text messages between an iPhone and an Android device, and could address a failure that has not been addressed for too long.
According to the Apple code discovered by Android Authority, iOS 26 will implement end -to -end encryption when sending messages using the RCS protocol between iOS and Android. Although you can currently send RCS messages between these two platforms (something that Apple finally caused in iOS 18), the standard is not encrypted from end to end. Although Imessage has presented this security technology for years, the GSM (GSMA) association, which implements and updates RCS, has taken time to add this hardened encryption.
That changed in March 2025, when the GSMA said that end -to -end encryption would be added to RCS. And although Apple previously described that end -to -end encryption would reach RCS on the iPhone in “Future Software currentations”, did not establish a date for change.
However, Android Authority says that the code that includes the “Gisrcsencrymentenabled” chain has been seen, suggesting that RCS encryption is experiencing internal tests in Apple. Additional code fragments also include the “MLS-RCS-series” chain, which could imply that Apple is evaluating the MLS encryption that Google has added to Google messages.
Despite the promising signs, there is no guarantee that iOS 26 will implement RCS encryption. Apple took a long time to implement RCS first, partly due to its weakest security compared to Imessage, and could be testing its updated functionality. But the fact that these chains are present in the iOS 26 code gives us the hope that RCS encryption may be on their way, making multiplatform text messages safer for iOS and Android users equally.
