RCS 4.0 update should let you ‘facetime’ between Android and iPhone

GSMA finalised RCS Universal Profile 4.0, introducing Messaging‑Initiated Video Calls (MIVC) for native in-thread 1:1 and group video, plus rich text formatting, higher-quality media encoding, and streaming-capable Rich Cards. If adopted, this could enable the first cross‑platform default-app video calls (Android-to-iPhone) and give brands richer in‑message commerce controls. Adoption is uncertain: neither Apple nor Google has committed and RCS 3.0 rollouts lagged, so realistic deployment is late 2026 to early 2027, limiting near-term commercial impact.

Analysis

The real economic lever here is platform control of the persistent conversation layer — whoever owns the default thread gains the right to embed commerce, identity signals, and low-friction media that redirect user attention and monetizable actions. If RCS becomes the cross‑platform default, that shifts durable monetization from app-level ecosystems (third‑party apps, payment flows, in‑app ads) toward carrier/OEM/business-messaging corridors and whoever powers the backend infrastructure (cloud, codec stacks, telco IMS). That migration would be slow but non-linear: a multi-year adoption curve with steep inflection once handset OEMs and one major OS vendor flips, because network effects scale quickly in messaging.

Timing and regulatory friction are the constraining variables. The marketplace is underweight the implementation risk: app incumbents will litigate, regulators will probe encryption and interoperability, and operators will monetize differently across regions — meaning localized rollouts and staggered monetization for 18–36 months. The high‑probability path is continued ambiguity through 2026 with concentrated upside after a single decisive OEM or large carrier bundle makes RCS mandatory, producing clustered product updates and a visible revenue cadence shift for infrastructure suppliers.

Second‑order winners are vendors that capture edge compute, codec acceleration, and business messaging orchestration (cloud, IMS vendors, adtech integration points), while losers include app-level engagement franchises that monetize via captive messaging threads. From a portfolio standpoint this is a long‑horizon structural change with discrete implementation catalysts; trade sizing should reflect binary event risk and multi‑quarter timing uncertainty.

Key Decisions for Investors

• Pair trade (12–18 months): Long GOOGL equity or Jan 2028 call spread (buy 1x 1,500 call, sell 1x 1,900 call) vs Short AAPL equity or buy Jan 2028 puts (protective put outright). Rationale: Google stands to capture infrastructure and data integration upside if Android/OEMs push RCS; Apple remains exposed to a loss of ecosystem leverage if it adopts or is compelled to interoperate. Risk/Reward: asymmetric — capped upside in spread limits cost; outright short of Apple is high risk if Apple resists successfully. Size to 2–4% portfolio.
• Event‑driven trade (6–12 months): Long select telecom infrastructure/software vendors (e.g., Ericsson/ERIC, Nokia/NOK, messaging platform vendors) via equity or call options timed to major carrier rollout announcements. Rationale: carriers will need server/IMS/cloud upgrades; catalysts are carrier/OS vendor trial announcements. Risk/Reward: medium risk — execution risk and multi‑vendor procurement cycles; target 2:1 reward/risk with tight stop at 12–15% drawdown.