Correct, the issue is that Apple doesn't support interoperability with iMessage or a modern standard like RCS. The EU is concerned enough to address this with a regulatory apparatus that the US lacks.
> Apple doesn't support interoperability with iMessage or a modern standard like RCS.
Sorry, but Google's proprietary closed source fork of RCS is not any kind of "standard".
> Google's version of RCS—the one promoted on the website with Google-exclusive features like optional encryption—is definitely proprietary, by the way. If this is supposed to be a standard, there's no way for a third-party to use Google's RCS APIs right now. Some messaging apps, like Beeper, have asked Google about integrating RCS and were told there's no public RCS API and no plans to build one.
Then Apple should allow interoperability with the iMessage protocol. They maintain control without the anti-competitive side effects. They are also free to use any variant of RCS that isn't controlled by Google.
This is very amusing given that Google wants to charge people to have RCS that can interoperate with their proprietary closed source implementation of RCS.
> If you want to implement RCS, you'll need to run the messages through some kind of service, and who provides that server? It will probably be Google. Google bought Jibe, the leading RCS server provider, in 2015. Today it has a whole sales pitch about how Google Jibe can "help carriers quickly scale RCS services, iterate in short cycles, and benefit from improvements immediately." So the pitch for Apple to adopt RCS isn't just this public-good nonsense about making texts with Android users better; it's also about running Apple's messages through Google servers. Google profits in both server fees and data acquisition.
Well, EU courts have recently ruled against Google's entire surveillance capitalism business model unless they convince users to opt in to ad tracking explicitly.
Try again.