RCS finally killed the green bubble problem, but carrier rollout is a mess

On May 11, 2026, Apple and Google each published nearly identical announcements: end-to-end encrypted RCS messaging had begun rolling out between iPhone and Android. For the first time, a text sent from an iPhone to an Android phone — or back — can be encrypted in transit, not just inside each platform's own app. That's a genuine milestone after years of Apple resisting full RCS adoption. It's also, right now, a feature most people don't actually have yet, even if their phones are new enough to support it.

What changed, specifically

RCS (Rich Communication Services) is the carrier-backed successor to SMS/MMS, supporting read receipts, typing indicators, high-resolution media, and group chat features that SMS never had. Apple added basic RCS support in iOS 18, but without encryption — meaning cross-platform messages were sent in the clear, unlike iMessage-to-iMessage traffic. The May 2026 update added end-to-end encryption using the Messaging Layer Security (MLS) protocol, so an iPhone-to-Android RCS message gets the same baseline privacy guarantee iMessage has offered for over a decade.

The catch: it's gated three different ways

This is the part that gets lost in “RCS is now encrypted!” headlines. The feature requires all three of the following simultaneously:

• OS version. Apple's rollout is tied to iOS 26.5 and later; it's still labeled Beta in Apple's own materials, meaning not every eligible device has received it yet even on the right OS version.
• Both parties' setup. Encryption only applies when both the sender and receiver have RCS (not SMS fallback) active and support MLS — if either side falls back to SMS, you lose both the rich features and the encryption.
• Carrier support. This is the biggest practical gap. The EFF's own description, as cited in current coverage, is blunt: RCS conversations are encrypted by default “as long as the carrier supports both RCS and encrypted messages.” Not every carrier does, and the gap is worse for prepaid and MVNO customers.

Historical analysis of iOS 18's RCS rollout found that Verizon, T-Mobile, and AT&T could handle RCS message transfer, while MVNOs like Google Fi and Mint Mobile reportedly could not. That data point predates the encryption rollout, so treat it as directional rather than current — but it illustrates the pattern: the big three postpaid carriers get support first, and budget/MVNO customers wait longer, sometimes indefinitely, depending on the host network's upgrade priorities.

Real-world friction people are already hitting

Support threads on Apple's own community forums describe RCS messages marked “Not Delivered” to Android recipients following recent iOS updates (specifically iOS 26.1/26.2 in user reports). Apple's own community responders have pointed to carriers as the responsible party for RCS and MMS delivery — which is technically accurate but not useful for a person whose message just didn't send. This is a structural problem with RCS as a standard: because it's carrier-mediated rather than purely an app-layer protocol like iMessage or WhatsApp, failures can originate in a layer neither Apple nor Google fully controls.

Apple still hasn't adopted the full standard

Apple's RCS implementation remains a subset of the GSMA's full Universal Profile; broader compliance is reportedly planned for later, but Apple has not committed to full parity on a fixed date. Critics have argued Apple's RCS support is deliberately partial — no cross-platform encryption until this year, and still no full feature parity with iMessage, with the green-bubble visual distinction unchanged. That criticism predates the encryption rollout and is now partially outdated, but the underlying asymmetry — iMessage-to-iMessage gets the full feature set, cross-platform does not — hasn't disappeared, it's just narrower than before.

There's also a regulatory backdrop worth knowing: Apple has faced DOJ antitrust scrutiny partly over messaging interoperability, and part of its posture shift toward RCS support in recent years tracks with that pressure, not purely technical readiness.

How to actually check if you have it

1. Confirm both phones are on current software — iOS 26.5+ for iPhone, and a current Google Messages version for Android.
2. In Google Messages, check chat settings for RCS chat status; on iPhone, check Settings > Apps > Messages > RCS.
3. Check your carrier's published feature list — Apple maintains a carrier support list, and it's worth consulting before assuming a failed or unencrypted message is a software bug rather than a carrier gap.
4. If a conversation shows a lock icon next to RCS indicators on either platform, that conversation is encrypted. Its absence doesn't necessarily mean failure — it may mean one party is still on SMS fallback.

The takeaway

Encrypted cross-platform texting is no longer theoretical — it shipped, and the cryptography behind it (MLS) is a legitimate, standards-based choice, not a proprietary workaround. But “shipped” and “universally working” are different claims. If you're advising a less technical friend or relative on whether their iPhone-to-Android texts are private, the honest answer in late 2026 is: probably not yet, unless you've verified both phones' software versions and both carriers' support — and even then, carrier-side delivery failures remain a known, unresolved friction point.