It isn't as simple as "apple bad, google good". Apple/iOS having E2EE is good. Apple refusing to cooperate at all in making E2EE interoperable with non apple products is bad. Google/Android having E2EE is good, and better than the claim above that RCS doesn't have E2EE by default. The fact that it is a proprietary extension is bad, but they seem more willing to interoperate. That said, if the positions were reversed, I suspect Google would also be more resistant to interoperability.
> That said, if the positions were reversed, I suspect Google would also be more resistant to interoperability.
With Apple adding support to iOS for RCS, the shoe is on the other foot.
That is because the core of their security model is a centralized key server, outside of the rest of RCS, that acts as the source of truth for an account and its associated public keys.
That fails once you have accounts which are not being authoritatively managed by Google, e.g. an email address with multiple messaging services attached, or a phone number which may be managed by any number of third party RCS installations. That is a problem which is still being actively solved.
Standardized interoperable E2EE
You don't get to arbitrarily send messages to the device of somebody on the other side of the world unless a 3rd party is providing those services.
That isn't exactly accurate. The standard doesn't have e2ee, but if you use google messages with RCS with other android phone it is end to end encrypted. But it uses a proprietary google extension to RCS. But I would be surprised if google wasn't willing to work with apple to get e2ee RCS working between iMessage and google Messages, but Apple has no interest in that.