RCS in iOS 18
This guide explains everything that you need to know about RCS, including how it works, how to use it on Apple devices, why you might not see it, why Apple decided to adopt it now, and the benefits that you can expect from RCS now that support for the feature is live.
[…]
Google’s implementation of RCS for Google Messages supports end-to-end encryption on Android devices, but it is worth noting that Apple is adopting the RCS Universal Profile created by the GSM Association and not a version of RCS modified by Google. RCS messages from iPhone to Android users are NOT encrypted at the current time.
iPhone-to-iPhone RCS messages don’t seem to be end-to-end encrypted, either. Unlike SMS, they do at least use TLS.
Videos, GIFs, and photos sent in messages between the two platforms now retain their original quality level, for example.
iPhone users also now see when an Android user you’re in a chat with is typing, prior to their finished message appearing, and they will see the same when you’re typing. Read receipts and delivery notifications between platforms now work as they have done when chatting with iPhone users.
It’s also now seamless for both iPhone and Android users to add and manage participants in a group chat originated on either platform. Scheduling messages to Android device users the way you can to Apple users is still not possible — but Apple claims that is a problem with RCS.
[…]
The ability to send a message to an Android user when using in-flight Wi-Fi or when the Wi-Fi connection is less than rock-solid doesn’t work properly.
Satellite texts work for iMessage and SMS—but not RCS, as Apple says that the packet sizes are too large.
RCS is also supposed to support emoji reactions from Android users, but it wasn’t working properly when iOS 18 launched. It’s not clear what changed, but The Verge says that something that Google or Apple tweaked made it work as of this week.
Apple introduced RCS support with iOS 18. However, full functionality will depend on carrier support. The good news is that major U.S. carriers like Verizon, T-Mobile, and AT&T already support RCS. Apple also has a list of carriers that support RCS on its website.
- Open Settings on your iPhone and select Apps at the bottom of the menu.
- Tap Messages.
- Under “Text Messaging,” select RCS Messaging.
- Toggle RCS Messaging to the green ON position if it isn’t already enabled.
Henry (via Hacker News):
I can’t help but feel RCS is almost indistinguishable from an OTT service at this point, controlled almost end-to-end by Google, who is driving the specification evolution, and both the only relevant server implementation and Android client.
[…]
On the iOS side, things are a bit more complex. Right now the RCS client is compatible with Universal Profile version 2.4, which is 5 years old.
[…]
On a more annoying note, RCS is still pretty far from being enabled worldwide. Like with other IMS configuration, the feature needs to be set up in iOS carrier bundles.
Due to unclear reasons, this is still not the case in many countries. Even in the US, some MVNO subscribers can’t use RCS yet.
It isn’t the first time Apple selectively delays standard IMS features. It’s a bit hard to believe carriers are at fault here, especially the ones that have been running their own Jibe deployment for years and have publicly communicated about the upcoming iOS support.
Stephen Schenck (via Hacker News):
Last year, Google announced its support for Messaging Layer Security (MLS), a new standard that promises to keep end-to-end encrypted (E2EE) messages secure across apps and platforms, in one-on-one and group chats alike. We’re finally starting to see the fruits of that effort, as references to MLS appear in the Google Messages app.
Developed by the Internet Engineering Task Force (IETF), the big problem MLS attempts to solve is E2EE group messaging. Google has already extended rich-communications services (RCS) to support E2EE for groups, and while it remains to be seen exactly how MLS will be integrated into Messages, we can hope to see it leading to more robust, secure communication across not just platforms, but supporting all your favorite apps.
The GSM Association (GSMA), the organization responsible for developing the Rich Communication Services (RCS) standard, announced on Tuesday that it is working to implement end-to-end encryption (E2EE) for messages sent between Android and iPhone devices, though no specific timeline for the implementation has been provided.
The news comes on the heels of Apple’s recent adoption of RCS with the launch of iOS 18, which replaced SMS with RCS messaging for texts sent to Android users. While the update brings improvements such as high-resolution media sharing, read receipts, and typing indicators, it notably lacks end-to-end encryption.
[…]
Currently, not all RCS providers offer E2EE. Google Messages, which enabled E2EE by default for RCS conversations last year, is one of the exceptions.
RCS rolled out in a relatively early beta release for my iPhone — perhaps in July — and I have appreciated both typing indicators and read receipts when chatting with friends who do not have iPhones.
[…]
However, I have at least two questions. The first: how will users be able to tell the difference between a private RCS discussion and one which is not end-to-end encrypted? Apple has several visual indicator options. For example, a message thread could have a persistent padlock or bubbles could use a different colour. Both add a layer of visual complexity which could raise questions or add confusion.
Perhaps a simpler choice would be better. The placeholder text in the compose box, for example, now says “Text Message • SMS” or “Text Message • RCS” depending on which protocol is being used. Surely it could also say something like “Encrypted • RCS” and, if Apple wanted to, it could make iMessage threads match with an “Encrypted • iMessage” placeholder.
An obvious answer would be to make encrypted RCS blue, like iMessage, since it’s far more similar to iMessage than to SMS, but no one seems to expect Apple to do that.
There’s a huge disconnect when you meet anyone that doesn’t have or use the same communication app you do. When your only option to reach someone is through an app you rarely use, you’ll rarely reach out.
SMS exists on all cell phones. It’s not just a built-in app, it’s a built-in service through your telecom provider. It’s default functionality on a network level.
SMS is outdated, insecure, and sucks, but it works on everything. If you swore off
Previously:
- US Officials Recommend Encrypted Messaging Apps
- iOS 18
- RCS in iOS 18 Beta
- Apple to Add RCS Messaging in iOS 17 Update
- Time for Apple to Fix Texting
- Blue Bubble Envy Is Real
- Google Messages Adds End-to-End Encryption
6 Comments RSS · Twitter · Mastodon
Thanks for this summary and the previous one covering RCS along with the Gruber post. I felt that his(Gruber's) post missed quite a bit of info on the Apple side of things and didn't really provide a fair comparison. However, it's good that this is being highlighted recently given the recommendation to consider E2EE in messaging. Given your and his reach on the web, more people will start talking about it again.
When the FBI tells Apple users not to text Android users not text each other "FBI: Android and iPhone Users Shouldn’t Text Each Other https://www.macobserver.com/news/fbi-android-and-iphone-users-shouldnt-text-each-other/ then you know that RCS is all but useless until end-to-end encryption is built into both platforms.
I’m on iOS 18.1 and I have no such setting for RCS in Messages settings. Maybe it’s limited to specific verified carriers? I only see the normal option for defaulting back to SMS if iMessage is unavailable.
@Sam from what I've read it's up to the carrier to support RCS or not.
I think it was similar for Android until Google somehow made it so that everyone jag RCS.
At this point it does seem like Apple is the one holding up RCS support for MVNOs, especially Google Fi. They say they have given Apple the information they need for the carrier profile, and it seems likely that they have. And as mentioned, Apple has seemingly purposely delayed carrier profile updates before out of no clear reason other than anti-competitive pettiness. Google very obviously supports it and has for some time. They've been bugging Apple to support it for years. Not that I have a lot of faith in Google, but that combined with Apple's history makes it seem clear to me.
Google Fi had the same problem with 5G for many years until India complained. Apple representatives went to India and then magically in the very next update, after years, 5G was enabled for lots of MVNOs. It wasn't even Google specific, it was about an Indian MVNO, but somehow Apple suddenly seemed to care.
Also not everyone on Android has RCS even if their carrier supports it. They have to use Google Messages. Textra claims no one else can make an RCS supporting client on Android, and according to the lack of any other option I can find, they are right.
