Apple unveiled the highly anticipated RCS (Rich Communication Services) standard to the iPhone as part of iOS 18 at their annual developers conference (WWDC 2024). RCS, alike SMS & MMS is a messaging standard for mobile phones developed by the GSMA (Global System for Mobile Communications) non-profit organisation. RCS has been a universal standard since 2016.
According to online reports, Apple's decision to add RCS is rumoured to have been made from geopolitical pressure from China, rather than Apple's more publicly known battles with legislation in the European Union (EU) or pressure from Google.
RCS, at least on paper is a no-brainer improvement that fixes everything wrong with texting between iPhone and Android. RCS has seamless group chats, read receipts, typing indicators, high quality media and the ability to use reactions.
Yet, there is one fundamental problem with RCS. RCS is not end-to-end encrypted. That is despite popular belief that RCS is an end-to-end encrypted standard; rather Google's proprietary implementation of the GSMA's RCS standard has encryption using Google Messages on Android. Despite this, Google has been heavily pushing Apple to implement RCS with #GetTheMessage.
Google crossed a line and no one noticed.
Out with the old (SMS & MMS) and in with the new. RCS is a modern standard that provides end-to-end encryption and supports high quality videos and photos in texts — because your group chat should be about keeping up with friends, not a debate about bubble colors. #GoogleIO
As of publishing, a staggering 0 of 43 replies seem to have picked up on the fact that Google is being deceptive on X about RCS being end-to-end encrypted stating "RCS is a modern standard that provides end-to-end encryption".
Intentional or not, Google has successfully misled the public, and they have done nothing to correct the record.
There is a big difference between purporting a truthful message to gain a competitive advantage versus misleading the public with no representation of the truth. There is no suggestion that this post is specific to Google Messages, and if anything, Google suggest RCS on iOS is E2E encrypted in regard to bubble colours, a common critic of messaging with Apple devices.
This monopolistic behaviour is yet more reason that it is paramount that the US DOJ (Department of Justice) should follow through with their considerations to break up Android from Google in relation to the ongoing United States v. Google LLC (2023).
SMS & MMS aren't E2E encrypted, so why does it matter that RCS isn't?
The widespread lack of knowledge and misinformation around RCS is an extensive issue and creates an uncomprehending privacy and security risk that affects almost every individual on the planet with a smartphone. It is the false confidence and incentive to switch from a secure third-party to the insecure native RCS implementation that is the real issue.
A lack of end-to-end encryption is not something you can just brush off. You may have nothing to hide, but you may have or will send or receive a message that includes personal, sensitive or confidential information. Privacy is a fundamental human right, and it should be protected above the self-centered interests of big tech. Do you really care that much about typing indicators?
If you use an iPhone, it is in both you and your contacts' best interest to disable RCS. If you can't use iMessage or Google Messages' implementation of RCS, you should be using a third-party app that is end-to-end encrypted such as Signal.
There is distant hope.
Google and RapidSOS have announced that they will roll out RCS based text-to 911 in the USA. Although this is only applicable to the USA, it is an exception to where you should re-enable RCS and is a real positive of the technology.
As mentioned before, the US Department of Justice may step in and break up Android from Google. This would prevent the spread and creation of further alleged disinformation regarding RCS like Google has done.
GSMA has announced that they're working on end-to-end encryption for RCS, but the timeline is unclear and even then, it'll take some time to implement and roll-out across iOS and Android devices before it's safe to use for everyone.