{"id":46068,"date":"2024-12-06T14:29:46","date_gmt":"2024-12-06T19:29:46","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=46068"},"modified":"2024-12-24T18:28:41","modified_gmt":"2024-12-24T23:28:41","slug":"rcs-in-ios-18","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2024\/12\/06\/rcs-in-ios-18\/","title":{"rendered":"RCS in iOS 18"},"content":{"rendered":"

Juli Clover<\/a>:<\/p>\n

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.<\/p>

[…]<\/p>

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.<\/p><\/blockquote>\n\n

iPhone-to-iPhone RCS messages don’t seem to be<\/a> end-to-end encrypted, either. Unlike SMS, they do at least use TLS.<\/p>\n\n

Charles Martin<\/a>:<\/p>\n

Videos, GIFs, and photos sent in messages between the two platforms now retain their original quality level, for example.<\/p>

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.<\/p>

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.<\/p>

[…]<\/p>

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.<\/p><\/blockquote>\n\n

Dan Moren<\/a>:<\/p>\n

\n

Satellite texts work for iMessage and SMS—but not RCS, as Apple says that the packet sizes are too large.<\/p>\n<\/blockquote>\n\n

Juli Clover<\/a>:<\/p>\n

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<\/a> says that something that Google or Apple tweaked made it work as of this week.<\/p><\/blockquote>\n\n

Tim Hardwick<\/a>:<\/p>\n

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<\/a> on its website.\n<\/p>

  1. Open Settings on your iPhone and select Apps<\/strong> at the bottom of the menu.<\/li>
  2. Tap Messages<\/strong>.<\/li>
  3. Under “Text Messaging,” select RCS Messaging<\/strong>.<\/li>
  4. Toggle RCS Messaging<\/strong> to the green ON position if it isn’t already enabled.<\/li><\/ol><\/blockquote>\n\n

    Henry<\/a> (via Hacker News<\/a>):<\/p>\n

    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.<\/p>

    […]<\/p>

    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.<\/p>

    […]<\/p>

    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.<\/p>

    Due to unclear reasons, this is still not the case in many countries.\nEven in the US, some MVNO subscribers can’t use RCS yet.<\/p>

    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.<\/p><\/blockquote>\n\n

    Stephen Schenck<\/a> (via Hacker News<\/a>):<\/p>\n

    \n

    Last year, Google announced its support for Messaging Layer Security<\/a> (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.<\/p>\n

    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.<\/p>\n<\/blockquote>\n\n

    Tim Hardwick<\/a>:<\/p>\n

    The GSM Association (GSMA), the organization responsible for developing the Rich Communication Services (RCS) standard, announced<\/a> 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.<\/p>

    The news comes on the heels of Apple’s recent adoption of RCS with the launch of iOS 18<\/a>, 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.<\/p>

    […]<\/p>

    Currently, not all RCS providers offer E2EE. Google Messages, which enabled E2EE by default for RCS conversations last year, is one of the exceptions.<\/p><\/blockquote>\n\n

    Nick Heer<\/a>:<\/p>\n

    \n

    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.<\/p>\n

    […]<\/p>\n

    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.<\/p>\n

    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.<\/p>\n<\/blockquote>\n

    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.<\/p>\n\n

    Louie Mantia<\/a>:<\/p>\n

    \n

    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.<\/p>\n

    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.<\/p>\n<\/blockquote>\n\n

    Eric Schwarz<\/a>:<\/p>\n

    \n

    SMS is outdated, insecure, and sucks, but it works on everything<\/em>. If you swore off Facebook<\/s> Meta like I did? Anyone who lives on WhatsApp, Instagram, and Facebook<\/s> Messenger is off-limits. Asking someone to sign up for a specific service because you’re the one person they know who uses it? Not gonna happen.<\/p>\n<\/blockquote>\n\n

    Previously:<\/p>\n