The long-awaited day is here: Apple has announced that its Messages app will support RCS in iOS 18. The move comes after years of taunting, cajoling, and finally, some regulatory scrutiny from the EU.
Right now, when people on iOS and Android message each other, the service falls back to SMS — photos and videos are sent at a lower quality, messages are shortened, and importantly, conversations are not end-to-end encrypted like they are in iMessage. Messages from Android phones show up as green bubbles in iMessage chats and chaos ensues.
Apple’s announcement was likely an effort to appease EU regulators.
The bubbles will remain green. At the very least, it’s handy a hand way to tell if chat is unencrypted.
But rcs can be e2ee right?
Encryption was never part of the RCS standard, and Google has been gatekeeping the encryption solution that they’ve been using… which is why there aren’t a lot of E2EE RCS clients floating around.
Google finally conceded several months ago, and now encryption will be part of RCS and managed by an independent working group that Google, Apple, and others can contribute to.
Phase 1 of RCS is about implementing the unencrypted foundation of the protocol. Encryption is supposed to come when the working group has aligned.
I wouldn’t hold my breath.
The whole RCS thing is a Bad Idea™ . It’s a standard by the GSM Association, which consists of over 1150 members (750 operators and 400 other companies). Getting all these companies to align will take forever.
To illustrate: the RCS initiative was started in 2007 and the steering committee was formed in early 2008. The first version of the Universal Profile, that would enable interoperability between different operators and networks was released in 2016. It took 8 f-ing years to come up with an interoperable messaging standard to replace SMS. It was intended to be implemented by operators, but since hardly any operator did Google had to run their own service, bypassing the network operators, just to get it off the ground. Operators are now slowly beginning to support it.
If Apple decides to add a feature to iMessage, they implement the feature, roll out an update to their servers and release it to a billion users in the next iOS update. If they want to add a feature to RCS, they first have to discuss it in the committee until they agree on a solution, this alone takes forever. Then every player needs to update their software to add support. This means potentially 750 operators who need to update their shit, and that is after their software suppliers add support for it. In the mean time, the new feature will work for some users when they communicate with some other users, depending on which phone and operator each party has. Rinse and repeat for every new feature you want to add.
This means RCS will at best only ever be a very basic messaging service. It’ll be an improvement over SMS and MMS, but that’s not saying much. It will be in no way a threat to Apple’s dominance in messaging.
Thank you for detailing what’s wrong with RCS.
It’s too little, too late, with major issues.
I was running XMPP on my phone in 2009…
Not across vendors it can’t. Or at least isn’t.
Well that sucks
deleted by creator