Verizon and T-Mobile say Pixel 4 won't support RCS messaging on their networks at launch
The rollout of RCS messaging has been an absolute mess - to the point where Google is actually taking things over from carriers. Now, there's more bad news. Google's Pixel 4 won't support RCS …
Context & Ripple Effects
RCS has been stuck in carrier-by-carrier fragments since Google first switched it on for Sprint devices in 2016 — a rollout whose RCS never interworked with AT&T, T-Mobile, or other carriers' implementations. Verizon then enabled RCS for the Pixel 3 on its own network in late 2018 (the same carrier-flagship pairing now failing for the Pixel 4), and Google extended support to its Fi network and a short device list in January.
The Pixel 4 news lands a week before the four national carriers announce the Cross Carrier Messaging Initiative to unify RCS across their networks in 2020 — an implicit admission that per-carrier enablement, the model that just left Google's new flagship without RCS on two of them, wasn't working.
First-order effects
- Pixel 4 buyers on Verizon and T-Mobile lose upgraded messaging features like read receipts and richer media at launch, even though Verizon had already shipped RCS for the Pixel 3 a year earlier.
Second-order effects
- Carrier fragmentation pushes Google to take RCS deployment into its own hands rather than wait on operator integrations, while Verizon, AT&T, T-Mobile, and Sprint counter with the Cross Carrier Messaging Initiative to standardize rollout across all four networks in 2020.
Third-order effects
- If carrier-led enablement keeps stranding flagships, control of Android's default messaging layer migrates from operators to Google and industry consortia, reducing carriers to pipes in the conversation stack they once owned.
The trend: Carrier-controlled RCS is giving way to platform-led and consortium-managed messaging, as each failed per-operator rollout shifts leverage toward Google and cross-carrier standards bodies.