/
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

Google says that RCS messaging in the Messages app for Android has 500M+ MAUs, and implores all mobile OSes to “upgrade”, in a dig at Apple

9to5Google Ben Schoon

Context & Ripple Effects

This milestone caps a three-year build-out: after rolling RCS out to all Android users in the US in late 2019, Google has grown the protocol inside its own Messages app to half a billion monthly users — and is now using that number as leverage, publicly telling every mobile OS vendor to 'upgrade' with Apple clearly the target.

The framing matters because it precedes the escalation to come: months later Google would launch the Get The Message campaign attacking SMS/MMS quality gaps like low-resolution media and missing encryption, and by late 2023 the same metric would double past 1B MAUs. This post is where the pressure strategy gets its quantitative ammunition.

First-order effects

  • Apple faces its first explicit, numbers-backed public callout on messaging: Google is arguing that iMessage's refusal of RCS degrades conversations between iPhone and Android users, turning a technical interop question into a consumer-facing grievance.
  • For carriers and Android OEMs, Google's MAU figure validates RCS as a deployed reality rather than a spec — the default messaging app on most new Android devices now runs it at scale.

Second-order effects

  • If Apple stays out while Google keeps publishing growth numbers, the burden of proof shifts: every green-bubble complaint now maps to a measurable installed base Google can cite, raising the cost of continued refusal ahead of any regulatory scrutiny of messaging interoperability.
  • Rival messaging apps (WhatsApp, Telegram) watch a first-party protocol gain distribution they cannot match on Android defaults, pressuring them to differentiate on features RCS lacks — end-to-end encryption chief among them.

Third-order effects

  • The pattern points toward messaging fragmenting along protocol lines rather than app lines: if RCS adoption keeps compounding through Android defaults, cross-platform texting could consolidate around carrier-grade standards, leaving Apple's walled garden as the outlier rather than the norm.
  • Sustained public pressure campaigns backed by usage data are becoming Google's playbook for forcing interop concessions from Apple — a template likely to extend beyond messaging into other Apple-controlled boundaries.

The trend: Google is converting RCS from a carrier rollout into a scale-backed standard-setting campaign, using user-count milestones as leverage against Apple's iMessage exclusivity.

Discussion

  • @reneritchie Rene Ritchie on x
    @markgurman There are a few decent reasons (unless today means they've been fixed?): 1. No encryption on group messages? 2. The spec is very high on carrier monetization and very low on security/privacy 3. Unclear how it runs without Google in the middle right now?
  • @reneritchie Rene Ritchie on x
    @MaxWinebach @markgurman That's true! But it doesn't solve for 1:n encryption and Apple already runs iMessage servers, so why run both? Shouldn't carriers get their act together and offer RCS as a true replacement for SMS, but with security and the increased features? Then it rea…
  • @maxwinebach Max Weinbach on x
    @reneritchie @markgurman Apple could host their own universal profile servers with the same specs as google