The Android developer just published an updated landing page for Google Messages, showing off key features ranging from customization, privacy and security, and, of course, AI.
On this landing page, there are different sections for each feature set, including one for RCS. As spotted by 9to5Google, if you expand this list of RCS features and scroll to the bottom, you see a section on “Coming soon on iOS: Better messaging for all.” That’s no surprise: We’ve known Apple was adopting RCS since November. However, it’s the next line that brings the news: “Apple has announced it will be adopting RCS in the fall of 2024.”
Of course, this does not say a lot as it is “in the fall” which is anywhere over a couple of months, and Google has tried to embarrass Apple into making moves before. I suppose, though, there is the looming court case against Apple which is anyway keeping pressure on Apple. If it were not for the US court case, I would have guessed Apple may have pulled out after the EU had ruled Apple was not a dominant player in the market (although the EU case was looking more at interoperability with WhatsApp and others in Apple Messages).
Of course, with Apple actually including RCS now, they can probably argue that there is interoperability via RCS between their platform and Android too. It must be remembered that in many countries, like mine, SMS’s are paid for so are very expensive to use for any form of chatting, and the costs go up exponentially when you text an international number.
I personally have quite a few issues with interoperability with Apple:
- I still have AirTags from when I had an iPhone and I daily get the audio beeps warning me the AirTags are not connected (I use an Android phone and alternate between an iPad and an Android tablet)
- I can’t wait to sell my AirTags and get the new one’s Google was working on that will interoperate with Apple, but supposedly Apple has been delaying building in that support into their devices (which Google already built into Android for AirTags in 2023)
- Because I was on Apple Messages and my iPad still sometimes connects, I find a message on my iPad that arrived a week ago which I had not seen (I had Beeper which was solving this problem)
Apple is not at all dominant outside the USA, but it makes interacting with Apple users quite a pain, as Apple has gone out of their way to try to keep their users inside the walled garden.
See https://lifehacker.com/tech/google-just-revealed-when-apple-will-officially-adopt-rcs
#technology #RCS #Apple #interoperability
But it is. SMS works via operating system exposing an API for developers for the phone modem interface. Google Messages is just an internet messaging app, just instead of using Internet standards like XMPP (from creators of Email and IP) it uses carrier’s standards which are mainly made with carriers being required in mind.
If you don’t believe me get a blocklist for all Google’s IP addresses and you’ll see Google Messages would stop working. Or just do anything with root account and Google server would stop allowing the app to work (https://www.theverge.com/2024/3/1/24087418/google-messages-blocking-rcs-on-rooted-android-devices).
The implementation in the real world is a mess, especially because the carriers have basically outsourced implementation to Google rather than trying to actually implement it themselves.
Right now, Google controls the entire stack (mobile OS, specific app, service provider). Still, once Apple implements a service provider (and locks it to their own mobile OS and app), that should allow for an opportunity for another to set up their own service provider that interfaces properly with either Google or Apple servers. And then that service provider would be able to provide an interface for any OS, any app, through an open API.
I would advocate for the path forward to be truly federated RCS providers being able to operate at will, where the accountholder of any phone number could affirmatively choose which RCS service provider to use (akin to how a domain owner can configure their domain to use a specific server for email to that domain, whether it’s self hosted or a cloud service provided by a big tech corporation like Google or Microsoft, or a smaller provider like Proton). Or at least, with number portability, let people choose small phone providers (like MVNOs) that compete on RCS implementation.
But I’m not holding my breath for that. I’d assume we’re currently on a path towards a duopoly, where Google provides the service for everyone on Android, and Apple provides the service for everyone on iPhones. Not clear what happens with “landline”/VOIP providers not locked to mobile devices, though, especially the commercial systems for corporate/enterprise users.
Google’s own one may be, and that is their right, but it is an open standard so anyone can produce their own RCS app like Samsung has done, and the same way Apple is building support into their exiting app. Nothing should stop a 3rd party developer looking at the standard, and producing an open source RCS app?
Yes, but Google basically owns all the servers. That’s why Apple didn’t want to join it.
Also the fact that nobody outside of the US cares about SMS or RCS, we never use it for anything else than getting appointment notifications from systems without apps and outdated 2FA.
Not really so, as MSMS is a major thing by us (outside the US) for most notifications from banks, gov, transactions, visit to pharmacy, etc. Incoming is fine apart from fact it is all open for anyone to read, but replies cost money. Also, where people are not using the same messenger, then it is sms text messages, each costing money. For pre-paid phone accounts, those SMSS messages cost even a bit more. SMS today is still the common denominator everything falls back on. It is very expensive when you consider what is paid, and it is only around 140 characters vs data.
As it is now the word “standard” is doing a lot of heavy lifting. Google themselves aren’t even done with the specs so it’s not trivial to support all functions when they are not described. So there’s plenty of problems for 3rd party. A bit of info here.
It is certainly not where it needs to be yet.