Google Just Revealed When Apple Will Officially Adopt RCS
lifehacker.com
Google just announced that Apple will be adopting RCS in fall of 2024. If this is true, it's likely Apple is planning RCS adoption as part of iOS 18.

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

  • NobodyElse@sh.itjust.worksEnglish
    121·
    9 months ago

    So is this going to be standard RCS, which has no encryption and the telcos need to support, or the Googlified version that does E2E encryption but requires storing keys on Google’s servers?

    RCS has interoperability issues itself and Google hasn’t been making the situation better.

    • ryper@lemmy.caEnglish
      161·
      9 months ago

      Apple is apparently working on getting encryption added to the standard

      In a background briefing with reporters, Apple spokespeople touted the company’s recent announcement that it will support the RCS messaging standard for iMessage sometime during 2024. In order to attend Apple’s briefing and view a background document, we had to agree to paraphrase the company’s remarks instead of quoting them directly.

      Apple clarified that it is not implementing RCS as it exists today because it doesn’t believe the standard offers enough privacy and security. Apple said it is working with a standards body—this is likely a reference to the GSMA—to ensure that the version of RCS it eventually implements will support encryption and strong privacy and security.

      Apple said that once it adopts RCS, iPhone and non-iPhone users will be able to exchange messages with higher-resolution photos and videos, and will experience improved group texting. Apple said it hasn’t brought its own message app to non-Apple devices because the user experience wouldn’t meet the company’s standards and that it cannot ensure that a third-party device’s encryption and authentication are secure enough.

    • abrinael@lemmy.worldEnglish
      2·
      9 months ago

      I suspected this is what was going on because of the way some of the documents were worded, but I can’t find any direct reference to it. Do you have any? Re: storing encryption keys on google’s servers.

      • NobodyElse@sh.itjust.worksEnglish
        2·
        9 months ago

        On my phone, so links may come later. It’s hard to find solid documentation on it, since their encryption extension is proprietary, but it’s been referenced as being based on the Signal Protocol. The Signal Protocol, or every implementation of it that I’ve seen, uses a central “trusted” repository of public keys to tell message originators query to encrypt the message to. For Signal, and I assume Google RCS, that central repository is Google. The protocol doesn’t allow for federation, so any system that is interoperable with Google RCS will rely on Google as the trusted authority.

        The private key part I’m much less sure of, since both the Signal and Google RCS clients are closed source. Signal makes you jump through hoops to add a new client, involving one of your currently installed clients. This suggests that Signal isn’t in possession of your private keys. On the other hand, all you need to set up a new Google client is your account password. This suggests that either your keys are held by Google (perhaps encrypted by your account password) or that new keys can be added without needing explicit involvement from current keys.

        Of course this is all speculation because the implementations aren’t available for inspection.