Cross-Platform Texting Finally Works, and the Interesting Part Is What Still Doesn’t

The migration to RCS as the default cross-platform messaging protocol resolved the most visible complaint in mobile messaging: photos and videos sent between different phone ecosystems no longer arrive as compressed, artifact-ridden files, and basic delivery and read status now work regardless of which platform is on the other end. That fixed a genuinely bad user experience that had persisted for years for no technical reason other than one major platform's reluctance to adopt an open standard it did not control. What did not travel with that fix is end-to-end encryption. RCS supports it within a single platform's implementation, but a message crossing between two different companies' RCS implementations currently falls back to unencrypted transport, because the encryption layer each vendor ships is proprietary rather than part of the interoperable core standard. That is a meaningfully different security posture from what users experience within either platform alone, and it is not something the green-bubble/blue-bubble framing — which was always about aesthetics and file quality — communicated to anyone. The standards body responsible for RCS has continued extending the specification, and cross-platform encryption has moved from "not addressed" to "specified but not universally shipped," which is the same intermediate state most cross-vendor standards pass through before full interoperability. Reactions, typing indicators, and read receipts sit in a similar place: technically part of the newer spec revisions, inconsistently implemented depending on which two apps are actually talking to each other, so a feature that behaves identically on both ends within one ecosystem can degrade or disappear entirely across ecosystems. The broader lesson echoes earlier interoperability fights in messaging and file formats: the highest-visibility complaint gets fixed first because it is the one users notice and complain about loudly, while the properties that are harder to observe directly — encryption guarantees, metadata handling, feature parity — lag well behind and require a second, much quieter round of standards and pressure to close. For a user deciding how much to trust a cross-platform conversation, the practical guidance has not changed much: check whether a specific conversation shows an end-to-end encrypted indicator rather than assuming platform-to-platform RCS carries the same guarantees as messaging within one company's app.