iOS 26.3 Hints at Improved iPhone-to-Android Texting Coming Soon

[MacRumors]

Starting with the iOS 26.3 beta, Apple appears to be laying the groundwork for carriers to be able to support end-to-end encryption (E2EE) for RCS messages, and that news should actually have even bigger implications for the Messages app on the iPhone.

In order to offer E2EE for RCS, iOS 26.3 or later would need to support RCS Universal Profile 3.0, which includes many iMessage-like enhancements for RCS:

• End-to-end encryption, which will prevent Apple and any other third party from being able to read messages and attachments while they are being sent between devices, as has always been the case with iMessage
• In-line replies
• Edit messages
• Unsend messages
• Full-fledged Tapback support for RCS messages, with no special workarounds

RCS support as a whole was added to the iPhone with iOS 18, which supported ‌RCS‌ Universal Profile 2.4. It is effectively a modernized version of the SMS standard, which remains available as a fallback option for text messages over a cellular network.

The enhancements listed above were actually introduced in RCS‌ Universal Profile 2.7, and iOS would finally get them by jumping to RCS Universal Profile 3.0.

iMessage conversations with blue bubbles have already supported end-to-end encryption by default since iOS 5. iMessage has also supported in-line replies since iOS 14, while the options to edit and unsend iMessages were introduced with iOS 16.

Timing

Last year, Apple said it planned to add support for end-to-end encrypted RCS messages to the Messages app in future iOS, iPadOS, macOS, and watchOS software updates. However, Apple did not provide a specific timeframe.

As mentioned above, Apple appears to finally be laying the groundwork for E2EE for RCS in the iOS 26.3 beta, but it will be up to carriers to implement support, and Apple might also work with Google to ensure there is a consistent experience across iOS and Android. Hopefully we begin to see support roll out at some point between iOS 26.3 and iOS 27.

E2EE for RCS may be limited to select countries at first, as carriers begin rolling it out.

Article Link: iOS 26.3 Hints at Improved iPhone-to-Android Texting Coming Soon

 

[LightProtector]

I’m glad, these are basically everything else I wanted from RCS.

 

[danielsutton]

Starting with the iOS 26.3 beta, Apple appears to be laying the groundwork for carriers to be able to support end-to-end encryption (E2EE) for RCS messages, and that news should actually have even bigger implications for the Messages app on the iPhone.

In order to offer E2EE for RCS, iOS 26.3 or later would need to support RCS Universal Profile 3.0, which includes many iMessage-like enhancements for RCS:

• End-to-end encryption, which will prevent Apple and any other third party from being able to read messages and attachments while they are being sent between devices, as has always been the case with iMessage
• In-line replies
• Edit messages
• Unsend messages
• Full-fledged Tapback support for RCS messages, with no special workarounds

RCS support as a whole was added to the iPhone with iOS 18, which supported ‌RCS‌ Universal Profile 2.4. It is effectively a modernized version of the SMS standard, which remains available as a fallback option for text messages over a cellular network.

The enhancements listed above were actually introduced in RCS‌ Universal Profile 2.7, and iOS would finally get them by jumping to RCS Universal Profile 3.0.

iMessage conversations with blue bubbles have already supported end-to-end encryption by default since iOS 5. iMessage has also supported in-line replies since iOS 14, while the options to edit and unsend iMessages were introduced with iOS 16.

Timing

Last year, Apple said it planned to add support for end-to-end encrypted RCS messages to the Messages app in future iOS, iPadOS, macOS, and watchOS software updates. However, Apple did not provide a specific timeframe.

As mentioned above, Apple appears to finally be laying the groundwork for E2EE for RCS in the iOS 26.3 beta, but it will be up to carriers to implement support, and Apple might also work with Google to ensure there is a consistent experience across iOS and Android. Hopefully we begin to see support roll out at some point between iOS 26.3 and iOS 27.

E2EE for RCS may be limited to select countries at first, as carriers begin rolling it out.

Article Link: iOS 26.3 Hints at Improved iPhone-to-Android Texting Coming Soon

Does this include the “Schedule Send” feature?

 

[fatTribble]

I wonder if Android phones will require an update or if they already support this?
Anyone? Bueller? 🤭

 

[Kar98]

I’d be happy just for

Change log: we finally fixed our godawful autocorrect.

 

[fguerraz]

End-to-end encryption, which will prevent Apple and any other third party from being able to read messages and attachments

Technically it’s not true, it makes sure that only Apple can read your messages. iMessage, iOS, and iCloud have access to the clear text messages.

Of course it would be very ill advised for them to do so and get caught, but technically that’s what it is, in particular with closed source software.

 

[ruslan120]

using what keyboard? fix typing first

 

[BarrettF77]

This was supposed to be out in 2025. Not sure why Apple can’t seem to make any deadlines they set anymore. RCS3.0 I think was announced in march of 2025 and out by end of year. Odd they weren’t able to make that happen.

They also need to address the auto correct issue from iOS 18/26 as they both are terrible.

 

[WarmWinterHat]

Technically it’s not true, it makes sure that only Apple can read your messages. iMessage, iOS, and iCloud have access to the clear text messages.

Of course it would be very ill advised for them to do so and get caught, but technically that’s what it is, in particular with closed source software.

Enable advanced data protection, and they don't. I've had it on since day one.

 

[Acapulco]

No privacy anymore

 

[bluecoast]

I wonder when Apple will make it possible to change the colour (yes I'm British) of SMS / RCS?

This would be good UX i.e. to have iMessage, SMS, RCS (and maybe MMS) to each have their own default colour.

Even better would be to let people change these colours to suit their own preferences (you know, like nearly every other messaging app out there).

The white on green for SMS is not particularly legible for most users.

It's one of the unappealing things that modern Apple does i.e. try to ensure lock in to iMessage by dragging their heels with the SMS / RCS experience.

And since I'm British, I am duty bound to say that this doesn't matter too much outside of the USA anyway, since everyone else uses WhatsApp as a lingua franca between android and iphone (although having time limited access codes being delivered securely will be most welcome for anyone).

 

[WarmWinterHat]

No privacy anymore

Communication privacy is a relatively new concept. Phone calls since the beginning have never been private; all took was a phone, alligator clips and a bored teenager to listen in (experience talking there), or back with party lines, your neighbor could easily listen. Cordless phones were easily listened to with a scanner for years. Mail still requires a warrant to open, but it sure is easy to steal if one tries. Email has never been private. Web data was free-and-clear for a long time until https became widespread.

If you want private, talk face to face.

 

[MrSnirf]

Technically it’s not true, it makes sure that only Apple can read your messages. iMessage, iOS, and iCloud have access to the clear text messages.

Of course it would be very ill advised for them to do so and get caught, but technically that’s what it is, in particular with closed source software.

That is false.

E2EE means the messages are all encrypted in transit as well as at rest until decrypted by the decryption key which only exists on device. All your messages are encrypted on device and in iCloud. The problem is that if you enable iCloud device backups, it also backs up that decryption key so technically Apple can use that decryption key in certain circumstances and at the request of law enforcement. If you enable advanced data protection, Apple does not have access to any of your encryption keys.

Standard data protection is the default setting for your account. Your iCloud data is encrypted in transit and stored in an encrypted format at rest. The encryption keys from your trusted devices are secured in Apple data centers, so Apple can decrypt your data on your behalf whenever you need it, such as when you sign in on a new device, restore from a backup, or recover your data after you’ve forgotten your password. As long as you can successfully sign in to your Apple Account, you can access your backups, photos, documents, notes, and more.

If you enable Advanced Data Protection for iCloud, the key does not exists anywhere else but on device.

Starting with iOS 16.2, iPadOS 16.2 and macOS 13.1, you can choose to enable Advanced Data Protection to protect the vast majority of your iCloud data, even in the case of a data breach in the cloud.

With Advanced Data Protection, the number of data categories that use end-to-end encryption rises to 25 and includes your iCloud Backup, Photos, Notes, and more. The table below lists the additional data categories that are protected by end-to-end encryption when you enable Advanced Data Protection.

If you enable Advanced Data Protection and then lose access to your account, Apple will not have the encryption keys to help you recover it — you’ll need to use your device passcode or password, a recovery contact, or a personal recovery key. Because the majority of your iCloud data will be protected by end-to-end encryption, you’ll be guided to set up at least one recovery contact or recovery key before you turn on Advanced Data Protection. You must also update all your Apple devices to a software version that supports this feature.

 

[Böhme417]

They should also include a tutorial for Android people on how to enable RCS. Of the few Android people I message, more than half of them aren’t using RCS.

 

[cyberhusky]

E2EE for RCS may be limited to select countries at first, as carriers begin rolling it out.

Carriers can switch on/off E2EE in RCS. So it makes no sense. Orange the biggest carrier in Europe won‘t allow E2EE

 

[WarmWinterHat]

@cyberhusky

As I understand it, they added the switch because in some countries, it's against the law to have EE2E SMS/RCS. Why Orange chooses to disable it, I have no idea.

 

[TimFL1]

This was supposed to be out in 2025. Not sure why Apple can’t seem to make any deadlines they set anymore. RCS3.0 I think was announced in march of 2025 and out by end of year. Odd they weren’t able to make that happen.

They also need to address the auto correct issue from iOS 18/26 as they both are terrible.

All Apple said was "in a future update", which was a drastic change of wording compared to them announcing adding RCS support 3 years ago (where they were actually specific about it launching in fall 2024).

I wonder when Apple will make it possible to change the colour (yes I'm British) of SMS / RCS?

This would be good UX i.e. to have iMessage, SMS, RCS (and maybe MMS) to each have their own default colour.

Even better would be to let people change these colours to suit their own preferences (you know, like nearly every other messaging app out there).

The white on green for SMS is not particularly legible for most users.

It's one of the unappealing things that modern Apple does i.e. try to ensure lock in to iMessage by dragging their heels with the SMS / RCS experience.

And since I'm British, I am duty bound to say that this doesn't matter too much outside of the USA anyway, since everyone else uses WhatsApp as a lingua franca between android and iphone (although having time limited access codes being delivered securely will be most welcome for anyone).

Back when they revealed RCS coming to iOS, they went out of their way to say it‘ll be green and grouped with SMS/MMS due to the lack of E2EE. By that logic, they have to change coloring, but I doubt they‘ll do that.


This article is very optimistic that Apples "we‘ll support E2EE" equals RCS UP 3.0 when their current 2.4 implementation isn‘t even fully compliant to begin with. Knowing Apple, they add E2EE but without all the baggage that comes with UP 2.7-3.0 and call it a day (malicious compliance).

There is no reason the 2.7 user facing features like reactions or replies can‘t be in by now with the basic non-E2EE encryption, there certainly seems to be no code traces of any new features coming to RCS other than E2EE (remember: there is an entire telephony messaging sdk for apps in the EU to take over RCS etc texting, that has nothing of value to facilitate reactions etc.).

 

[dkh587]

All Apple said was "in a future update", which was a drastic change of wording compared to them announcing adding RCS support 3 years ago (where they were actually specific about it launching in fall 2024).


Back when they revealed RCS coming to iOS, they went out of their way to say it‘ll be green and grouped with SMS/MMS due to the lack of E2EE. By that logic, they have to change coloring, but I doubt they‘ll do that.


This article is very optimistic that Apples "we‘ll support E2EE" equals RCS UP 3.0 when their current 2.4 implementation isn‘t even fully compliant to begin with. Knowing Apple, they add E2EE but without all the baggage that comes with UP 2.7-3.0 and call it a day (malicious compliance).

There is no reason the 2.7 user facing features like reactions or replies can‘t be in by now with the basic non-E2EE encryption, there certainly seems to be no code traces of any new features coming to RCS other than E2EE (remember: there is an entire telephony messaging sdk for apps in the EU to take over RCS etc texting, that has nothing of value to facilitate reactions etc.).

The fact that they haven't gone past 2.4 is very telling that they aren't really interested in advancing unless they absolutely have to.

Obviously, Apple doesn't want us being able to edit, add in-line replies etc or do anything close to iMessage as long as they can hold out on it...

 

[Black_Mage]

"End-to-end encryption"

That's exciting until you learn about something called client-side scanning that can render encryption useless. I have no doubt that Google is already using it on Android phones, but continue to enjoy your illusion of privacy.

 

[tyrnnsrs]

What version of RCS are most carriers using nowadays?

 

[Black_Mage]

Communication privacy is a relatively new concept.

Something else that's relatively new is the ease with which government and big tech can collect, categorize, analyze, and recall all the information they intercept. It's a bit scary.

 

[germanbeer007]

no thanks. how about we just delete RCS? infinitely better and simpler.

 

[TimFL1]

The fact that they haven't gone past 2.4 is very telling that they aren't really interested in advancing unless they absolutely have to.

Obviously, Apple doesn't want us being able to edit, add in-line replies etc or do anything close to iMessage as long as they can hold out on it...

Apple is obviously doing what gives them the best bottom line. Wouldn’t surprise me if they mix and match UP versions to get their highground in terms of texting.

What version of RCS are most carriers using nowadays?

Whatever flavor Google is on, 2.7 - 3.0 (uncertain if Google rolled out all changes). No single carrier has their own RCS hub on iOS, they are all using Jibe as their backend.

 

[user1234]

That’s great and all but lots of carriers still don’t have RCS support. None in Sweden do yet. People use other messaging platforms so there’s very little incentive to spend the money on setting up RCS services in their network.

RCS has been a mess since day 1. It was never a required part of the standard to be supported by carriers, google didn’t get them interested and rolled their own service which ment carriers has even less intensive to set it up themselves and then Apple launches RCS support using the standard and everyone complains Apple hasn’t enabled it for all carriers even though those carriers don’t offer the service.

It would be great to be able to send high resolutions photos to the 3 people I know with Android phones though.

 

[cmichaelb]

Enable advanced data protection, and they don't. I've had it on since day one.

Where is that in the settings?