RCS has a credibility problem. For years, the pitch was “SMS but better” — rich media, read receipts, typing indicators, group chat. The features were real, but deployment was a mess. Carriers built RCS in silos, which meant your “upgraded” messages only worked if both people happened to be on the same carrier.

That’s finally changing. The first half of 2020 has produced genuine interoperability milestones, and honestly? They’re worth paying attention to.

T-Mobile and Google: Universal Profile Goes Live #

In late May, T-Mobile announced a partnership with Google to bring RCS Universal Profile messaging to all T-Mobile and Metro by T-Mobile Android users. Here’s why the details matter: this isn’t T-Mobile building their own RCS infrastructure. They’re connecting to Google’s Jibe platform, which means T-Mobile users get cross-network interoperability with every other carrier on Jibe.

That’s a meaningful shift. Before this, T-Mobile had their own RCS implementation that only worked T-Mobile to T-Mobile. Now their users can exchange RCS messages with anyone on a Jibe-connected carrier globally.

Sprint had actually gone further before the merger — they preloaded Google Messages (formerly Android Messages) on all new devices starting in 2017, making Sprint the first major US carrier with true Universal Profile support. With the T-Mobile/Sprint merger completing this year, the combined subscriber base on Universal Profile is substantial.

Why does Jibe matter so much? Google’s Jibe Hub acts as a carrier-grade interconnection point. Instead of each carrier building bilateral interconnects with every other carrier — an O(n^2) problem that scales terribly — carriers connect to the hub once and reach all hub-connected operators through a single integration. It’s the same architectural pattern that made email interoperable: centralized relay points that reduce bilateral negotiation to zero.

Mavenir: P2P Interconnect Across 13 Countries #

The second milestone is arguably more impressive from a technical standpoint. Mavenir completed peer-to-peer RCS interconnection between Telefonica, Vodafone, and Deutsche Telekom Germany. The numbers matter here: an estimated 158 million subscribers across 13 countries now have RCS interoperability between these three carrier groups.

The GSMA announced this in February 2020 as part of a broader push on RCS interconnection, but the Mavenir implementation stands out because it demonstrates hub-based P2P interoperability at real scale. Mavenir’s Mobile Business Messaging Cloud sits between the carriers, handling the protocol translation and message routing that makes cross-carrier messaging work.

What makes this different from previous RCS deployments? The words “peer-to-peer.” Earlier RCS implementations focused on application-to-person messaging — businesses sending messages to consumers. P2P means person-to-person: regular users messaging each other across carrier boundaries. That’s the use case that actually matters for replacing SMS.

The GSMA Universal Profile: Why Standards Matter #

Both deployments build on the GSMA’s Universal Profile specification. Understanding the spec matters because it’s what makes interoperability possible.

Before Universal Profile, RCS had too many configuration options. Carriers could implement different subsets of the RCS feature set, which meant two carriers both “supporting RCS” might have incompatible implementations. The Universal Profile reduced the option space; it defines a specific feature set and a specific way to implement it so that conforming implementations are interoperable by default.

The spec covers core messaging features — chat, group chat, file transfer, audio messaging — plus the signaling and authentication protocols that carriers need to connect. It also defines how IPX providers — the companies handling traffic exchange between carriers — can participate in RCS interconnect.

By simplifying the technical options, the Universal Profile turned RCS interoperability from a bilateral negotiation problem into a conformance problem. If two carriers both implement Universal Profile 1.0 correctly, their users can exchange RCS messages. Period.

Where We Actually Stand #

As of mid-2020, RCS has reached approximately 90 operators in 60 countries globally. That sounds impressive, but context matters. “Reached” means different things for different operators — some have full Universal Profile deployments with interconnect, while others have limited rollouts or operator-specific implementations that don’t interoperate.

The Android side is more coherent these days. Google Messages supports RCS with a carrier-independent fallback through Jibe, which means even users on carriers that haven’t deployed RCS can get the features if they install Google Messages. The coverage gap is shrinking.

The fragmentation that remains is mostly on the interconnect side. Two carriers might both support Universal Profile, but if they haven’t established an interconnection — either bilateral or through a hub like Jibe — their users still fall back to SMS when messaging each other.

What I’m Watching #

From an engineering perspective, three things stand out about the current RCS trajectory.

First, the hub model is winning. Bilateral interconnects don’t scale; hubs do. Google’s Jibe Hub and Mavenir’s interconnect platform both prove this. The question is whether the industry consolidates around one hub or fragments across several.

Second, the subscriber numbers are getting real. 158 million users across Telefonica/Vodafone/DT is not a pilot. T-Mobile’s US subscriber base is not a test market. These are production-scale deployments with actual traffic.

Third, the pace is accelerating. The GSMA’s February announcement highlighted multiple operators interconnecting simultaneously, not one at a time. That suggests the technical barriers to interconnect are dropping as implementations mature and hub infrastructure improves.

RCS still has gaps. The interoperability story is incomplete, and the user experience varies significantly by carrier and device. But the milestones from the first half of 2020 suggest the ecosystem is moving past the “promising standard with fragmented adoption” phase into something that looks more like actual infrastructure.

I’m cautiously optimistic. The engineering problems are solvable. The coordination problems — getting dozens of carriers to agree on implementations and establish interconnects — are harder. But the momentum is clearly there.