edevans.org

The State of RCS

RCS Interoperability — Why Messaging Is Still Broken in 2026

Cross‑platform messaging is still broken in 2026 because the companies responsible for fixing it never had the incentive to do so. RCS was supposed to replace SMS, but carriers dragged their feet, Google built its own version, and Apple resisted interoperability to protect iMessage’s lock‑in. Even Apple’s new “RCS support” is intentionally limited — no cross‑platform encryption, no feature parity, and the green bubble stigma remains. Fixing this will require enforced standards, real interoperability, and likely regulatory pressure. Until then, messaging stays the last—and most political—broken piece of the mobile experience.

I. Introduction — The Problem

For more than a decade, the mobile industry has failed to deliver something that should be simple in 2026: a universal, modern, secure way for people to message each other across devices. Every other part of the smartphone experience has evolved dramatically — cameras, processors, displays, AI — yet the basic act of sending a message between an iPhone and an Android phone still falls back to a protocol from the 1990s.

SMS and MMS remain the default cross‑platform fallback for billions of messages every day. They are insecure, unreliable, and technologically obsolete. They strip out photos, break group chats, fail silently, and offer none of the features people expect from modern messaging. And despite the industry’s promises, RCS — the supposed successor — has never fully replaced them.

RCS was meant to fix everything. It was pitched as the universal upgrade: typing indicators, high‑resolution media, read receipts, encryption, and a consistent experience no matter which phone you used. But instead of becoming the global standard, RCS became a patchwork of incompatible implementations, half‑supported features, and political battles between companies that benefit from the status quo.

Apple resisted it for over a decade. Carriers dragged their feet, then abandoned the effort. Google pushed ahead, but only by building its own version of RCS that bypassed the very carriers who were supposed to run it. And now, even with Apple’s “support,” the experience is still fractured — because Apple’s implementation is intentionally incomplete.

The result is a messaging landscape defined not by technology, but by business incentives and ecosystem politics. The divide between iMessage and everything else has become cultural as much as technical. The blue bubble vs. green bubble distinction isn’t just a UI choice; it’s a symbol of fragmentation, stigma, and the power dynamics that keep messaging broken.

This article explores how we got here, why RCS interoperability remains unsolved, and what it would actually take to fix the last broken piece of the mobile experience.

II. The Current State of RCS (2026 Snapshot)

In 2026, RCS exists in an awkward middle state: technically deployed, widely available, and yet still not delivering the universal, seamless messaging experience it was designed to provide. On paper, RCS should have replaced SMS years ago. In practice, it functions more like a patch layered on top of a broken foundation — one that works well in some scenarios and falls apart in others.

At its core, RCS is meant to bring modern messaging features to the default texting apps on smartphones: typing indicators, high‑resolution media, read receipts, group chat reliability, and encryption. And to be fair, Android‑to‑Android messaging has reached that point. Google’s RCS implementation — built through its Jibe platform — is consistent, encrypted, and feature‑rich. If every device used Google’s version, the story would be very different.

But that’s not the world we live in.

Google’s RCS vs. the GSMA Universal Profile

The GSMA’s “Universal Profile” was supposed to define a single, interoperable standard. Instead, it became a loose set of guidelines that carriers implemented inconsistently, partially, or not at all. Google eventually stepped in and built its own RCS stack, effectively bypassing carriers and creating the only version of RCS that actually works reliably.

This solved one problem — fragmentation among carriers — but created another: Google’s RCS is now the de facto standard, not the GSMA’s, and Apple has no incentive to match Google’s implementation feature‑for‑feature.

Apple’s RCS Rollout: Support in Name, Not in Spirit

Apple’s long‑awaited adoption of RCS was framed as a step toward interoperability, but the reality is far more limited. Apple supports the bare minimum required to avoid regulatory scrutiny and public criticism. The result is a version of RCS that:

In other words, Apple’s RCS is not designed to create a great cross‑platform experience — it’s designed to create a better green bubble, not an equal one.

The Real User Experience Today

If you’re messaging between two Android phones, RCS works well. It feels modern, fast, and secure. But the moment an iPhone enters the conversation, the experience degrades:

The technical limitations are frustrating, but the psychological ones are worse. Even with RCS, the green bubble remains a symbol of “less than,” reinforcing the divide Apple has spent years cultivating.

III. A Brief History of RCS

To understand why RCS interoperability is still a mess in 2026, you have to understand where it came from — and more importantly, who it was designed to serve. The short version: RCS wasn’t built for users. It was built for carriers trying to protect their turf. That decision shaped everything that followed.

The GSMA Origins (2007–2012): Carriers Try to Reinvent SMS

In the late 2000s, carriers saw the writing on the wall. Apps like BlackBerry Messenger and early versions of WhatsApp were proving that internet‑based messaging could do things SMS never could. Carriers feared losing control — and revenue — if messaging moved to the internet.

So the GSMA, the global carrier trade group, created RCS as a way to modernize SMS while keeping carriers in charge. The idea was simple: build a richer messaging protocol that carriers could operate, monetize, and control. But from the start, RCS suffered from:

It was a standard designed by committee, and it showed.

The Universal Profile Era (2016–2019): A Last Attempt at Standardization

By the mid‑2010s, RCS had become a fragmented mess. Different carriers implemented different versions, and none of them worked well together. The GSMA responded with the “Universal Profile,” a set of guidelines meant to unify RCS into a single, interoperable standard.

On paper, it was the right move. In practice, carriers still:

The Universal Profile was supposed to be the turning point. Instead, it became the moment the industry realized carriers weren’t capable of delivering a modern messaging platform.

Carriers Drag Their Feet

Carriers had no real incentive to invest in RCS:

So RCS stagnated. Years passed. Users moved on. And the carriers who were supposed to lead the transition quietly stepped back.

Google Takes Over (2019–2023): The Jibe Era

Eventually, Google got tired of waiting. In 2019, it effectively took control of RCS by rolling out its own implementation through the Jibe platform. Instead of relying on carriers, Google:

This solved the fragmentation problem — but only on Android. It also created a new dynamic: RCS was no longer a carrier‑run standard; it was a Google‑run standard.

Apple’s Decade‑Long Resistance (2011–2023): iMessage as a Strategic Weapon

Apple launched iMessage in 2011, and it quickly became one of the most powerful lock‑in mechanisms in tech. Apple had no reason to support RCS:

So Apple simply refused. For more than a decade, Apple ignored RCS entirely, even as Google, carriers, regulators, and users pushed for it.

It wasn’t until regulatory pressure — especially from the EU — became unavoidable that Apple finally announced RCS support. But even then, Apple made it clear: it would support RCS only on Apple’s terms, and only to the extent required to avoid legal trouble.

IV. Why RCS Still Isn’t Truly Fixed

Even in 2026, RCS remains a half‑implemented standard that works beautifully in controlled conditions and collapses the moment it encounters the real world. The problem isn’t that RCS is a bad technology. The problem is that no one with power has ever been properly incentivized to make it universal, consistent, or complete.

Technical Fragmentation

RCS was designed with optional features, optional encryption, optional server models, optional client capabilities — and optional compliance. That’s not a standard; that’s a menu. The result:

A universal messaging protocol cannot function when every participant gets to pick and choose which parts they feel like supporting.

Encryption: The Achilles’ Heel

End‑to‑end encryption is table stakes. But RCS encryption is:

The moment an iPhone enters a conversation, encryption disappears.

Business Incentives Misaligned With Interoperability

RCS failed not because it was technically impossible, but because interoperability is not profitable.

Every major stakeholder benefits from keeping RCS “good enough” but not great.

No Enforcement Mechanism

The GSMA can publish standards, but it cannot:

Without enforcement, RCS is more suggestion than standard.

SMS Fallback Still Dictates the Experience

Because RCS is not universal, every messaging app must be prepared to fall back to SMS/MMS at any moment. That fallback:

As long as SMS exists as the safety net, RCS can never fully replace it.

V. Apple’s Resistance: Strategic, Not Technical

Apple’s decade‑long refusal to support RCS was never about technology. It was about power. iMessage is one of the most effective ecosystem lock‑in mechanisms ever created, and Apple knows it. The company’s resistance to RCS — and its intentionally limited implementation once forced — is best understood not as a technical stance, but as a business strategy designed to preserve the moat around the iPhone.

iMessage as a Lock‑In Mechanism

iMessage isn’t just a messaging service. It’s a social platform, a status symbol, and a subtle but powerful form of ecosystem pressure. Apple has spent years cultivating the idea that iMessage is the “premium” messaging experience, and everything else is a downgrade.

Apple’s Public Arguments vs. Apple’s Real Incentives

For years, Apple justified its refusal to support RCS with arguments like:

But these were smokescreens. Apple could have helped shape RCS. It could have pushed for encryption. It could have driven adoption. Instead, Apple chose to sit on the sidelines because RCS threatened the exclusivity of iMessage.

Apple’s Intentionally Incomplete RCS Implementation

When Apple finally announced RCS support, it was not a victory for interoperability. It was a defensive maneuver — a way to avoid regulatory penalties while preserving the iMessage moat.

Apple’s RCS implementation is deliberately limited:

This is not a technical limitation. It’s a business decision.

Regulatory Pressure and Minimal Compliance

The EU’s Digital Markets Act (DMA) forced Apple to open up parts of its ecosystem. Messaging interoperability was one of the targets. Apple’s RCS announcement came only after regulators signaled they were considering iMessage a “core platform service.”

Apple’s response was classic Apple: comply just enough to avoid penalties, but not enough to change the power dynamics.

The Blue Bubble / Green Bubble Effect

This is the heart of Apple’s strategy — and the most culturally visible part of the messaging divide.

The blue bubble vs. green bubble distinction is not an accident. It’s a psychological signal engineered to create:

Even with RCS, Apple has kept the green bubble. And that’s the tell. Because if Apple truly cared about interoperability, the bubble color would be irrelevant. But Apple needs the green bubble to persist — not for technical reasons, but for cultural ones.

VI. Carrier Apathy and Lack of Support

If Apple’s resistance is the most visible reason RCS never reached its potential, the carriers’ apathy is the most foundational one. RCS was originally their project — their attempt to modernize SMS, protect revenue, and stay relevant in a world moving toward internet‑based messaging. But instead of leading, carriers dragged their feet, under‑invested, and ultimately abandoned the very standard they were supposed to champion.

Carriers Never Truly Wanted RCS to Succeed

Carriers approached RCS with the mindset of the early 2000s: messaging was a revenue stream, and any new standard needed to preserve that. But by the time RCS was ready for deployment, the world had changed.

Slow, Inconsistent, and Half‑Baked Rollouts

Carriers treated RCS like a checkbox, not a priority. They rolled it out slowly, inconsistently, and with missing features. A universal messaging standard cannot survive when its primary stewards treat it like an afterthought.

The Rise of OTT Apps Made Carriers Irrelevant

By the mid‑2010s, the messaging landscape had shifted decisively:

Users weren’t waiting for carriers to fix SMS. They had already moved on.

Outsourcing RCS to Google: The Moment Carriers Gave Up

When carriers realized they couldn’t maintain RCS infrastructure, they quietly handed the keys to Google. Google’s Jibe platform became the default RCS backend for most Android devices — not because carriers wanted it, but because they didn’t want to deal with it.

The Business Model Problem: No Money, No Incentive

At the end of the day, carriers are businesses. And RCS offered them:

Without a business model, carriers had no reason to invest in RCS — and every reason to let Google handle it.

VII. What It Would Actually Take to Fix RCS

Fixing RCS isn’t a matter of tweaking a protocol or shipping a software update. The problems are structural, political, and economic. To truly repair the messaging ecosystem — to finally replace SMS with something modern, secure, and universal — the industry would need to do something it has never done before: agree on a single standard, implement it consistently, and put user experience above corporate incentives.

A Single, Enforced Global Standard

RCS failed because it was too flexible. A real universal messaging standard needs mandatory encryption, mandatory feature parity, mandatory server behavior, and mandatory client capabilities.

True End‑to‑End Encryption Across Platforms

Encryption must be universal, mandatory, cross‑platform, and openly specified. This is the single biggest technical blocker — and the one Apple is least likely to cooperate on.

Apple and Google Agreeing on Feature Parity

For RCS to truly work, Apple would need to make Android messaging as good as iMessage. Apple has no incentive to do that voluntarily.

Carriers Stepping Aside Entirely

Carriers have proven they cannot run a modern messaging platform. Fixing RCS requires removing carriers from the critical path.

Regulatory Intervention

The only entity with the leverage to fix this is government. Regulators could require cross‑platform encryption, feature parity, interoperability mandates, and non‑discriminatory UX.

The Nuclear Option: Replace RCS Entirely

There’s a growing argument that RCS is too compromised to save. Instead of fixing it, the industry could adopt a modern, open protocol like MLS (Message Layer Security).

VIII. The Future: Three Possible Paths

With Apple’s partial RCS adoption, Google’s de facto ownership of the protocol, and carriers largely out of the picture, the future of cross‑platform messaging is at a crossroads.

1. Regulation Forces True Interoperability

Regulators classify messaging as a core interoperability service. Apple is required to support full cross‑platform encryption and feature parity. SMS finally dies.

2. Apple Maintains a Two‑Tier System

This is the most likely path if nothing forces Apple’s hand. RCS improves incrementally, but iMessage remains superior by design. The divide persists.

3. RCS Fades, Replaced by a Modern Open Standard

The industry acknowledges RCS is too compromised to fix. A new protocol — likely based on MLS — becomes the foundation for cross‑platform messaging.

IX. Conclusion

For all the progress the mobile industry has made, messaging remains the last fundamentally broken part of the smartphone experience. Not because the technology is hard. Not because the standards don’t exist. Not because users don’t care. Messaging is broken because the companies that control it benefit from keeping it that way.

RCS was supposed to be the fix — the universal upgrade that would finally replace SMS and bring modern messaging to everyone, regardless of device. Instead, it became a case study in misaligned incentives: carriers that didn’t want to invest, Google that couldn’t enforce compliance, and Apple that had every reason to resist interoperability.

Fixing this will require more than protocol updates or new features. It will require a shift in power — away from platform lock‑in and toward true interoperability. It will require regulators willing to challenge the status quo, companies willing to prioritize users over moats, and standards bodies willing to enforce consistency rather than suggest it.

The deeper question is whether we, as users, actually want that world. Interoperability means giving up some of the exclusivity,

Tags: