Earlier quoted context omitted.
> In the meantime, RCS is missing really basic capabilities. For example, RCS encryption only works for 1:1 conversations, so things like family chats are not private. As opposed to iMessage, but certainly not as opposed to SMS which is what RCS would actually be replacing on the iPhone. Apple would rather have EVERY conversation with an android user unencrypted rather than work towards a solution.
Apple is not standards-resistant, if that's what you're suggesting. Given their history of supporting standards (and occasionally leading a standard's adoption), that's clearly not the case. RCS is not a slam dunk. Juniper Research says RCS-capable subscribers represent less than 13% of global mobile subscribers in 2022. (They project that that will double to 40% by 2026, FWIW.) End-to-encryption is not part of the R…
Their historical position has hurt their own customers, android users, and the standardization process itself. RCS (or a different standard) would be in a completely different place if Apple in their US market leadership position had made an effort.
They could open the iMessage spec, they could publish an iMessage app for Android, or they could just contribute in good faith to the standardization process. Their hostility to this particular standardization process (I don't contest that Apple is happy to support many standards efforts, such as USB) is driven by profit to the detriment of pretty much everyone else.