The problem is many people assume that all messengers are drop-in replacements for each other when in reality they are all streamlined social networks with their own communities, unique technological infrastructure, and business models. The irony is that the DMA and DSA will decimate many of their business models more than forcing interoperability will weaken iMessage use on the iPhone.
Yep, people rail against the "indignity" of non-Apple users getting green bubbles in the Messages app, but this system will necessarily result in something similar - Apple
cannot verify the identity of a user sending a message from, say, WhatsApp, so the message will have to be presented as "Message from someone that WhatsApp says is named 'John Doe'". So, maybe a red bubble for these? And they won't have access to every "nice" feature of Apple's iMessage ecosystem, because it'll necessarily be a "least common denominator" of what the systems at both ends can support well enough to convert between the two.
(To be clear, Apple cannot just show these messages with whatever name WhatsApp sends, in a blue bubble - what if there's a name collision between the two - if you regularly get messages via iMessage from John Smith, your boss, and you get a message from your long lost college friend, John Smith, via WhatsApp, in Europe, clearly you don't want those two message streams combined - at the very minimum there would be massive confusion, at worst, there would/will be legal action against the messaging services for getting someone fired for replying to the wrong person, or for someone sneaking in via a gateway to masquerade as someone you know to get information - so... we'll need clear identifiers both that these messages are coming in over a gateway, and that all Apple can verify about the identity is that "WhatsApp says this is X".)
Most people seem to be thinking, "oh, well, that's just whether or not to include images and video". I'm thinking: differences in handling of character sets/encodings, length of text messages, image
formats and
sizes, video
formats and
sizes (and retention policies for both images and video - are they stored on a server? only on the local device? I'd bet different systems handle it differently), how to handle marking and displaying in-line replies, how, exactly, can text, images, and video be interspersed... let's see...
How to handle reaction tags that can be attached to individual messages (thumbs up/down, etc) - who decides on what the common set of reaction tags is? How do you handle the situation where someone local uses a tag that isn't part of the agreed-upon set, on a message going across the gateway? Do you not display it on the remote end? Do you display a text description of it instead? Do you prevent the local user from applying that reaction tag if there's anybody in the group chat that is connected through a gateway (or for simplicity do we go to having just one universal government-mandated allowable set of reactions on messages, going forward)? And if you prevent tags that can't go through a gateway, how do you deal with a gatewayed user being added to an existing chat where such tags have been used? Do you retroactively remove those tags from the chat? And if a gatewayed user is added to a group chat - first off, some systems support that and some don't, how do you resolve that - but, second, the larger issue, what system is responsible for passing the scroll back history of that chat to the gatewayed user, and, and how far back does it go?
I'm sure, given a little time and effort, there are dozens of additional collisions that can be added to this list.
You can, of course, reduce all this to a least common denominator of, "well, just allow text, no reaction tags at all, can't add gatewayed users to group chats mid-chat" - and... that would be precisely what we have now with SMS - and pretty much any smartphone on the planet can already send an SMS message to any other smartphone on the planet. So, if that's what they want, congratulations, mission accomplished.
If they want more than that, then they're going to have to understand that this idea of, "well, just provide a messaging API" is actually a pretty complicated and very messy proposition. It's going to be a lot more work than people expect, it isn't going to support many of the niceties that people on each system will assume that it ought to handle, and it isn't going to work as well as what is being sold to people with these regulations.
All of the drive to do this very much has the feel to it of a group of politicians / bureaucrats (who don't really have the technical background to understand the ramifications of what they're asking) who are being nudged/lobbied to push this through, by one or more companies that think they will gain something from the resulting changes, rather than - as it is being presented to the public - being in the best interests of the end users who will be affected.