Google is rolling out RCS advanced messaging to Android devices on Sprint, but Google's RCS doesn't work with RCS on AT&T, T-Mobile, and other carriers
There has been much noise made about Google's launch of its RCS messaging platform via the Messenger app on Sprint today.
Context & Ripple Effects
In late 2016 Google switched on RCS advanced messaging for Android devices on Sprint through the Messenger app — but only for Sprint, and crucially without interoperability with the RCS deployments AT&T, T-Mobile, and other carriers were building separately. That made this less a national launch than a single-carrier island, with Google's implementation and the carriers' implementations speaking past each other.
The fragmentation was the story's engine for years afterward: Google extended the platform with business messaging for Sprint users while the big four carriers answered with their own Cross Carrier Messaging Initiative in 2019, before Google rolled RCS out to all US users in the Android Messages app later that year. The endpoint of the arc is telling — by 2023 AT&T moved its default Android messaging onto Google's Jibe platform, effectively conceding the interop war to Google's stack.
First-order effects
- Sprint Android users gain rich messaging features inside Messenger, but only when texting other Sprint users — messages crossing to AT&T, T-Mobile, or other carriers fall back outside Google's RCS.
- Google's Messenger becomes the delivery vehicle for RCS on Sprint, putting Google's client rather than the carrier's own app in control of the messaging experience for those users.
Second-order effects
- Non-interoperable carrier RCS builds give AT&T, T-Mobile, Verizon, and Sprint an incentive to coordinate, which they eventually do via the Cross Carrier Messaging Initiative announced for a 2020 rollout.
- Google keeps investing unilaterally — adding business messaging so firms can reach Sprint RCS users — turning its fragmented footprint into a beachhead for a carrier-agnostic platform.
Third-order effects
- If the pattern holds, control of Android messaging migrates from carrier-owned RCS infrastructure to Google's server-side stack, which is where it lands by 2023 when AT&T defaults to Jibe for instant feature updates.
- Carrier-by-carrier fragmentation proves unsustainable for a protocol meant to replace SMS, pushing the industry toward either cross-carrier standards bodies or a single vendor's implementation as the de facto standard — here, both happened in sequence.
The trend: RCS in the US is consolidating from fragmented per-carrier deployments toward Google-controlled infrastructure, with carriers ceding the messaging layer one defection at a time.