/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Verizon, AT&T, T-Mobile, and Sprint announce the Cross Carrier Messaging Initiative to bring RCS to Android phones in 2020

Here's a shocker.  All four major US carriers — Verizon, AT&T, Sprint, and T-Mobile — have just announced that they're joining forces to deliver RCS messaging in the US for Android smartphones in 2020.

9to5Google Ben Schoon

Context & Ripple Effects

Carrier-run advanced messaging has been fragmented for years: when Google rolled out RCS on Sprint in late 2016, its implementation did not interoperate with the RCS services AT&T, T-Mobile, and others were running separately, leaving each network an island Google's Sprint-only RCS rollout.

This announcement is the four major US carriers attempting to fix that by fiat — pooling their networks under the Cross Carrier Messaging Initiative to make RCS work across Verizon, AT&T, T-Mobile, and Sprint Android phones in 2020, with the carriers rather than Google setting the terms.

First-order effects

  • Android users on all four networks become the immediate beneficiaries: rich messaging no longer stops at carrier boundaries, replacing the per-network silos that made cross-carrier RCS unusable.
  • Google's role shifts from broker to supplier — the carriers are claiming interoperability for themselves, which pressures the client side of the stack where Google ships Android Messages.

Second-order effects

  • AT&T and T-Mobile subsequently making Google's Android Messages the default SMS/RCS app shows the initiative converging on Google's client anyway, just through carrier defaults rather than a Google-led rollout carriers adopting Android Messages as default.
  • A working cross-carrier RCS baseline sharpens the question the carriers' own later statements raise: whether Apple will swap iMessage/SMS fallback behavior for RCS, since interoperability with Android is exactly what the initiative delivers Verizon joining the Android Messages default switch.

Third-order effects

  • The consortium model itself proved fragile — within roughly eighteen months, comments from Verizon, AT&T, and T-Mobile suggested the joint initiative had been quietly killed CCMI's collapse, with interoperability advancing instead through unilateral carrier decisions on defaults.
  • If that pattern holds, US messaging standards get set not by carrier joint ventures but by whoever controls the default messaging app on the handset — a structural win for platform owners over network operators.

The trend: US mobile messaging standardization is shifting from carrier consortia negotiating interoperability to platform-side defaults deciding it de facto.

Discussion

  • @backlon Dieter Bohn on x
    Look please read my rant about RCS but if you can't just know that it is summed up by this press image of the cross-carrier mobile payments company ISIS. It was easy to laugh when they messed up payments. It will not be when they messed up texting. https://www.theverge.com/...
  • @backlon Dieter Bohn on x
    Exclusive details on the big new joint venture from AT&T, Verizon, T-Mobile, and Sprint to support RCS on Android. They're making an app, they promise to work with Google, and more. Click: https://www.theverge.com/... https://twitter.com/...
  • @hallstephenj Stephen Hall on x
    Google: let's do RCS the right way! Carriers: Google: do it, or we will do it for you. Carriers: ok fine but we need to mess some things up first. also we would like all the credit and none of the blame. https://twitter.com/...
  • @maxwinebach Max Weinbach on x
    Starting in like late 2020, we are gonna have the RCS vs. iMessage wars in the US and it's going to feel *so* good. https://twitter.com/...
  • @bdsams Brad Sams on x
    I feel like we have heard this before. https://twitter.com/...
  • @backlon Dieter Bohn on x
    Google statement on the US carrier's surprise announcement that they're rolling their own RCS app, several hours after the initial press release. If you told me the carriers left Google out of it out of pique I wouldn't be surprised. https://www.theverge.com/... https://twitter.c…
  • @journeydan Daniel Bader on x
    Did the carriers just announce that they are going around Google to create an app-based messaging service based on the open RCS standard? This is diabolical. This is awful. And this will end badly. https://www.verizon.com/...
  • @benedictevans Benedict Evans on x
    I have lost count of how many failed efforts there have been to make RCS work. None of them ever had the slightest chance of working and this one won't either. https://www.theverge.com/...
  • @pierce David Pierce on x
    So to sum up, this is: - A new messaging app - Made by the carriers - Without Google and Apple Can't wait to use a crappy app to send messages to half my friends https://twitter.com/...
  • @agilethumbs Scott on x
    It's not end-to-end encrypted, so it doesn't matter. RCS is one of Google's greatest missteps. https://twitter.com/...
  • @caro_milanesi Carolina Milanesi on x
    🤔 cause when I think of a great user experience I think of carriers. Look at what they called this thing “Cross Carrier Messaging Initiative (CCMI)” and you can decide on how successful they will be. Now Google has a morale obligation to get something done to save us all!!! https…
  • @oneangryitguy Angry IT Guy on x
    “bUh tHe tExTs wIlL bE gReEn!” -Apple fanboys in the US https://twitter.com/...