- Message projects are much easier to find in iOS 26
- The disclosed code also suggests that iOS 26 will bring a huge boost of safety
- Apple apparently tests end -to -end encryption for RCS messages
How many times have you started writing a text in the application of iOS messages, then left it later, to forget who you send a message and what you said a few hours later?
It is a common event, but iOS 26 includes a new feature that will facilitate the search for these unfinished texts – and it is almost shocking that Apple did not implement it earlier.
There are also filters for other situations. If you have programmed messages for another time, you will see a filter send later, for example, although there is an unread filter for any message that you have not yet read.
Note that these filters only appear if there is a relevant message to filter. If you do not have drafts, for example, you will not see the filter of the drafts. And these filters work, whether you use iPhone iPhone messages to iPhone or RCS / SMS messages sent to Android devices. Blue bubbles or green bubbles, it works.
Stronger security
According to Apple Code would have discovered by Android authorityiOS 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 Apple finally caused in iOS 18), the standard is not encrypted from start to finish. While that has been presenting this safety technology for years, the GSM Association (GSMA) – which implements and updates RCS – has taken some time to add this hardened encryption.
This changed in March 2025, when the GSMA said that end -to -end encryption would be added to RCS. And although Apple previously stressed that end -to -end encryption would arrive at RCS on the iPhone in “Future software updates”, it did not set a date for change.
However, Android Authority says that it is seen from the code which includes the chain “GisrcSenCryptionABABLEDABLE”, which suggests that RCS encryption undergoes internal tests at Apple. Other code extracts also include the “MLS-RCS-Server” channel, which could imply that Apple evaluates the encryption MLS that Google 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 in the first place – partly because of its lower safety compared to Imessage – and it could simply test its updated functionality. But the fact that these channels are present in the iOS 26 code gives us the hope that RCS encryption could be on the way, which makes multiplaeal texts safer for iOS and Android users.
