RCS messaging is interoperable between iPhone and Android now, but the rollout has created a two-tier experience

Apple shipped RCS support across iOS starting in late 2024, and by 2026 the green-bubble-versus-blue-bubble divide that defined a decade of cross-platform texting friction is technically over. Messages between iPhone and Android now support read receipts, typing indicators, high-resolution media, and larger group chats without falling back to SMS. What's not over is the experience gap — and understanding exactly where that gap still lives matters more than the headline "RCS is here now" framing suggests.

The core issue is that RCS interoperability shipped as a floor, not a ceiling. Apple implemented the GSMA's RCS Universal Profile, the baseline standard, rather than adopting Google's proprietary extensions on top of it — and that gap between "RCS works" and "RCS works exactly like it does within a single ecosystem" is where most user confusion and carrier inconsistency now lives.

What Actually Got Fixed

The most visible improvement is media quality. SMS/MMS compressed photos and videos aggressively, often to the point of visible artifacting; RCS transmits media at much higher resolution, closer to what users expect from a modern messaging app. Read receipts and typing indicators — table stakes in WhatsApp, iMessage, and every other messaging platform since roughly 2015 — now work across the iPhone-Android boundary for the first time. Group messaging also improved substantially: RCS groups support larger participant counts and don't fragment into painful reply-all SMS threads the way mixed-platform group texts historically did.

Carrier-side rollout has been the binding constraint rather than device support. Most major US and European carriers have activated RCS on their networks, but activation isn't uniform — some prepaid and MVNO (mobile virtual network operator) plans still route messages through the older networks that don't support RCS at all, silently falling back to SMS with no user-facing warning beyond the color of the message bubble.

The Encryption Gap Nobody Talks About Enough

End-to-end encryption is the feature most likely to mislead users into a false sense of security. Apple's iMessage-to-iMessage traffic is end-to-end encrypted, and Google's RCS traffic between two Android devices using Google Messages is also end-to-end encrypted using an extension built on the Signal protocol. But RCS traffic crossing between an iPhone and an Android device is not end-to-end encrypted — it's encrypted in transit between each device and the carrier or platform infrastructure, then decrypted and re-encrypted at each hop, which is a materially weaker security guarantee than true end-to-end encryption.

The GSMA and both companies have discussed extending E2EE to cross-platform RCS traffic, and interoperable encryption specifications exist on paper, but production deployment across the full carrier and device ecosystem hasn't happened as of mid-2026. Users assuming their cross-platform messages carry the same protection as same-platform messages are working from an incorrect mental model, and neither Apple nor Google surfaces this distinction clearly in the UI — the message bubble simply looks like a normal RCS message either way.

The Two-Tier Reality

What's emerged in practice is a three-way tier rather than a clean binary. iMessage-to-iMessage conversations get the fullest feature set with true E2EE. Android-to-Android conversations through Google Messages get nearly the same feature set with true E2EE via Google's RCS extension. Cross-platform iPhone-to-Android conversations get most of the visible features — read receipts, typing indicators, high-res media, decent group chat — but without end-to-end encryption and with occasional feature gaps depending on which RCS profile version each carrier has actually deployed.

This creates a genuinely confusing situation for average users, who see a functionally similar-looking chat interface across all three tiers with no obvious visual cue about which security guarantees actually apply. The old green-bubble system was crude, but at least it was legible — users knew instantly they were on SMS/MMS with reduced features. The new system looks uniform on the surface while hiding materially different security and feature profiles underneath.

What This Means for Users and Businesses

For sensitive conversations, users should not assume cross-platform RCS carries the same protection as an intra-platform chat; a dedicated E2EE messaging app (Signal, WhatsApp) remains the more defensible choice when message content genuinely matters. For businesses building on RCS Business Messaging for customer communications — a growing use case for appointment reminders, delivery notifications, and support — the fragmented rollout means testing across multiple carriers and device combinations is still necessary rather than assuming uniform behavior once RCS is technically "supported."

Takeaways

• Check your carrier's specific RCS activation status — device support doesn't guarantee your plan actually routes RCS traffic, particularly on prepaid or MVNO plans.
• Don't assume cross-platform (iPhone-Android) RCS messages are end-to-end encrypted — they aren't yet, despite looking identical to same-platform encrypted messages in the UI.
• For sensitive conversations, use a dedicated E2EE app rather than relying on RCS across platforms.
• Businesses deploying RCS Business Messaging should test across carrier and device combinations rather than assuming uniform feature support.
• Watch for the GSMA's cross-platform E2EE specification reaching production — when it ships, it closes the single biggest remaining gap in RCS interoperability.