The RCS landscape in late 2021 looks nothing like it did a year ago. Not because of some flashy feature drop, but because the connectivity fabric — the actual plumbing that lets RCS messages flow between carriers — has hit a density that changes the math for operators still sitting on the fence.

I’ve been watching this space pretty closely, and honestly? The infrastructure story is more compelling than whatever new emoji reactions just shipped.

The US Carrier Consolidation #

The biggest shift this year has been AT&T finally adopting Google Messages as its default Android messaging app. T-Mobile did the same in 2020, so between them, we’re talking about a massive chunk of US Android users.

Verizon, of course, is still holding out. They keep shipping their own messaging app and maintaining their own RCS stack. What this means in practice: a T-Mobile subscriber texting an AT&T subscriber gets full RCS through Google’s infrastructure, but message a Verizon user and you’re probably falling back to SMS — depending on the device, the configuration, the phase of the moon. You know how it goes.

The pattern here is worth watching. Carriers initially resisted Google’s RCS infrastructure because, well, who wants to hand messaging control to a platform company? The Cross-Carrier Messaging Initiative (CCMI) was their attempt to build something carrier-owned, independent of Google. That initiative has effectively stalled. One by one, carriers have moved to Google’s Jibe platform instead, because building messaging infrastructure at scale turned out to be harder than anyone expected.

Was this outcome inevitable? I’m not so sure. But the economics clearly favored consolidation: Google was willing to pour money into infrastructure and give it away; carriers weren’t willing to collectively fund an alternative at the level needed to compete. Simple as that.

End-to-End Encryption Arrives #

In June 2021, Google Messages flipped on end-to-end encryption by default for one-to-one RCS conversations. They’re using the Signal Protocol — same one that powers Signal, WhatsApp, Facebook Messenger’s encrypted mode.

This matters for a couple of reasons.

First, it plugs the most legitimate criticism of RCS versus over-the-top apps: that RCS messages, while richer than SMS, weren’t actually encrypted between sender and recipient. Carriers and infrastructure providers could theoretically peek at content. That gap is now closed for 1:1 chats.

Second, the Signal Protocol choice actually means something. It’s been audited to death, it’s open-source, and it’s handled billions of messages across other platforms without major incidents. Google didn’t try to roll their own crypto — they went with the industry standard. That builds trust in a way some proprietary scheme never would have.

The catch — and it’s a real one — is that encryption stops at one-to-one conversations. Group chats? Still unencrypted. Google says group encryption is in development, but no timeline. For now, if you’re having sensitive group conversations, you still need a dedicated encrypted messaging app. Sorry.

The Jibe Hub Model #

This is the part of the RCS story that doesn’t get nearly enough attention.

Traditional carrier interoperability meant bilateral agreements. If Carrier A wanted to exchange RCS with Carrier B, they’d negotiate a direct interconnect. For N carriers to fully interoperate, you need N*(N-1)/2 bilateral connections. At 90+ operators, that’s over 4,000 bilateral agreements. Good luck with that.

The Jibe Hub solves this with a hub-and-spoke model. Each carrier connects to the hub once. Once they’re in, they can exchange messages with every other carrier on the hub. Adding a new carrier benefits everyone already connected — the network effect actually works in RCS’s favor for once.

The result: time-to-market for new carriers has dropped dramatically. Operators that would have spent months negotiating bilateral interconnects can go live in weeks now.

Some carriers have built direct peer-to-peer RCS interconnects outside the hub. Deutsche Telekom and Vodafone have a direct P2P connection in Germany, for example. This makes sense when you’ve got massive bilateral traffic volumes where the latency and control benefits justify the integration cost. But for most operators, the hub model is plenty good enough — and far simpler.

Global Footprint #

As of late 2021, RCS is live across 90+ operators in more than 60 countries. Coverage isn’t exactly uniform — Western Europe, North America, parts of Asia-Pacific are well ahead, while Africa and South America are still pretty sparse. But the trajectory is clear enough: RCS is shifting from “technology a few progressive carriers support” to “default messaging layer for Android devices worldwide.”

The carrier-independent fallback in Google Messages deserves a mention here. On Android devices where the carrier doesn’t support RCS natively, Google Messages can route RCS traffic through Google’s own servers (with user consent). This means an end user gets RCS features regardless of whether their specific carrier has deployed it. The carrier eventually catches up, or they don’t — but the user experience doesn’t depend on waiting around.

This fallback mechanism is arguably what accelerated adoption more than any standards body specification. Carriers that were slow to deploy RCS found their subscribers already using it through Google’s infrastructure. At that point, formally adopting Jibe becomes less of an investment decision and more of an acknowledgment of what’s already happening.

What This Means for the Messaging Ecosystem #

The infrastructure story in 2021 is consolidation around Google’s platform. Whether you see that as positive (interoperability, scale, encryption) or concerning (concentration of messaging infrastructure in one company) depends on where you’re standing.

From a purely technical perspective, the Jibe Hub model has proven itself. Message delivery is reliable, latency is acceptable, and the encryption implementation is sound. The carrier connectivity milestones of 2021 — AT&T’s adoption, the E2EE rollout, crossing 90+ operators — represent the point where RCS infrastructure moved from “promising” to “established.”

Features will keep evolving. Better media handling, richer business messaging, broader encryption coverage. But the hard part — building the connectivity fabric that makes any of those features useful at scale — is increasingly behind us.

What remains uncertain is the competitive landscape. RCS has the carriers and the default-on-Android advantage; iMessage has the Apple ecosystem lock-in; WhatsApp and others have the cross-platform install base. How these forces interact over the next few years will determine whether RCS becomes the universal messaging standard it was designed to be, or settles into that awkward niche of “Android default that iOS users never see.”

The infrastructure is ready. Whether that’s enough — well, that’s the question, isn’t it?