Apple added support for the Google-supported RCS (Rich Communication Services) message standard with iOS 18. RCS was created by the cellular industry to add advanced media and other features to messaging that would work across operating systems. Google adopted RCS in Android about five years ago, and it’s available for most phones that can run Android 5 (Lollipop, 2014) or later. The standard requires carrier upgrades, and nearly all have made them.
Turning on RCS for your iPhone lets Android users send and receive messaging information or formatting that previously was limited to Android-to-Android (via RCS) or Apple-to-Apple (via iMessage). This includes read receipts that show when the recipient has viewed a message (if they have that option enabled), emoji tapbacks, extremely long messages, and audio messages. (iMessages appear as blue bubbles in a Messages conversation and only work among people using Apple hardware. SMS, MMS, and RCS messages appear as green bubbles.)
You can enable or disable RCS in iPhone 18 via Settings > Apps > Messages > RCS Messaging. Disabling RCS doesn’t prevent you from communicating with Android users; instead, your iPhone reverts to interactions with them via SMS or MMS.
Opt in or out of RCS via Settings > Apps > Messages.
Foundry
Apple’s version of RCS doesn’t yet support group texting. It also lacks the end-to-end encryption available with supported Android-to-Android RCS and is mandatory for iMessage. Your iPhone to Android messages are sent as if they passed over a secure web connection: they are encrypted and decrypted by servers on either end instead of only on your devices and that of recipients. An industry effort is underway to create an encryption standard that Apple would be able to use.
This Mac 911 article is in response to a question submitted by a Macworld reader.
Ask Mac 911
We’ve compiled a list of the questions we get asked most frequently, along with answers and links to columns: read our super FAQ to see if your question is covered. If not, we’re always looking for new problems to solve! Email yours to [email protected], including screen captures as appropriate and whether you want your full name used. Not every question will be answered; we don’t reply to emails, and we cannot provide direct troubleshooting advice.
