The point of the exercise is for Google and Apple to maintain control over the ecosystem.

RCS is technically superior (protocol, transport, security, all of it) but is captured from the start on the technical level by design by the big players. From the perspective of the vast majority of users who have very limited technical awareness, it was silently slipped in as an upgrade at one point or another. This means that those not adopting the proprietary BigTech solution are perceived as being difficult by insisting on using software that's now perceived as outdated or as otherwise mildly incompatible.

▲

HybridStatAnim8 4 hours ago | parent | next [-]

GrapheneOS does not want to adopt RCS for public perception. It is still a better option than SMS/MMS and providing it is beneficial. GrapheneOS will still recommend using better platforms and protocols but RCS being bundled and cross platform are great reasons to implement it.

▲

george_perez 4 hours ago | parent | prev [-]

Eh, I don’t think you have to include Apple here. If it were up to them, the iPhone would still have zero RCS support right now. The current implementation of RCS, even in iOS 27 beta, is clunky.

To me, the only they’re trying to maintain control of is AppleOS-to-AppleOS text communication.

	▲	fc417fc802 2 hours ago \| parent \| next [-]
		> To me, the only they’re trying to maintain control of is AppleOS-to-AppleOS text communication. Yes, exactly. Apple and Google are both acting to maintain control and this has resulted in a standard that improves functionality but is effectively poisoned at the technical level. Left to their own devices I'm sure Apple would have preferred to stay with their original solution that is even more closed off.
	▲	anon7000 3 hours ago \| parent \| prev [-]
		Idk, I mean RCS on iPhone is just SMS/MMS but fixing like 90% of the issues. I don’t find it that clunky.