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
Google is bootstrapping rich messaging by going around the carriers: RCS advanced features arrive on Android through its own Messenger app, but only for Sprint subscribers, and only inside Google's implementation. That matters because Sprint is the lone carrier whose network Google can light up directly — AT&T, T-Mobile, and others run their own RCS stacks that Google's version cannot reach.
This single-carrier beachhead sets up the next decade of the story: Google later builds business messaging on top of the Sprint RCS base, the big four carriers counter with their own Cross Carrier Messaging Initiative, Google sidesteps them by pushing RCS server-side to every US Android user via Android Messages, and by 2023 even AT&T concedes, moving its default Android messaging onto Google's Jibe platform.
First-order effects
- Sprint Android users gain rich chat features through Messenger today, while users on AT&T, T-Mobile, and other carriers get nothing — and a Sprint user texting an AT&T RCS phone falls back to ordinary SMS because the two implementations do not interoperate.
Second-order effects
- The fragmentation forces the carriers to organize: Verizon, AT&T, T-Mobile, and Sprint form their own cross-carrier RCS effort in 2019, while Google keeps expanding unilaterally through app-level rollout rather than waiting for carrier agreement.
Third-order effects
- If the pattern holds, control of the RCS stack migrates from carrier networks to Google's platform layer — the endgame visible when AT&T adopts Jibe as its default, leaving carriers as pipes under a Google-operated messaging service.
The trend: Carrier-controlled messaging standards are being absorbed into a Google-operated platform, one unilateral rollout at a time.