Apple has been methodical in its approach to implementing RCS support across its messaging platforms. However, the company has yet to fully equip the iPhone with essential end-to-end encryption capabilities. In March, Apple committed to integrating end-to-end encrypted RCS messaging in the Messages app. Yet, even in the recent iOS 26 beta, messages remain unencrypted end-to-end, thereby exposing potential security vulnerabilities. The latest developer beta versions of iOS 26, iPadOS 26, macOS 26, and watchOS 26 have been made available for testing, which users can access through the Settings app on compatible devices.
Apple’s Delays in Implementing Encrypted RCS Messaging Raise Questions on Privacy Commitment
The introduction of end-to-end encryption for RCS was unveiled in March as part of version 3.0 of the RCS Universal Profile, which establishes a global standard for messaging features and specifications. By indirectly acknowledging the adoption of this updated version, Apple has indicated its alignment with modern privacy practices. Beyond encryption, RCS version 3.0 encompasses a suite of features akin to those found in iMessage, which were first introduced in version 2.7 of the Universal Profile.
Many of these features align closely with those already available in Apple’s iMessage on iPhone, iPad, and macOS. Furthermore, embracing the updated RCS standards would significantly benefit all users—whether they are on iOS or Android platforms.
- Native Tapback support for RCS messages without workarounds
- Capability to unsend messages
- Edit previously sent messages
- In-line replies
- End-to-end encryption for greater privacy and security
Google has dedicated considerable effort to persuade Apple to enhance its support for RCS on the iPhone, even resorting to advertisements and lighthearted mockery. Eventually, Apple recognized that adding RCS support would enhance communication for all users, including those on iOS, enabling smoother interactions with non-iOS devices. However, this move also implies a potential dilution of iMessage’s unique features, which traditionally attract a dedicated user base. From my perspective, Apple’s ecosystem is more expansive than just iMessage, and integrating support for Android could enrich the overall user experience. Nonetheless, it is essential to acknowledge that iMessage still retains a plethora of exclusive features, which will likely continue to evolve in upcoming updates—features that Android messaging platforms may never access.
Apple integrated initial RCS support with the release of iOS 18, but the current support only includes version 2.4. The ongoing debate between blue bubbles (iMessage) and green bubbles (SMS/RCS) remains lively, with no definitive solution in sight unless Apple radically shifts its strategy and introduces iMessage on Android—a scenario that seems unlikely. However, it is worth noting that Apple might adopt version 3.0 in subsequent iterations of the iOS 26 beta or the official release, leaving room for optimism among users.
Leave a Reply