Of course it's been Google's Android, I don't think anyone ever questioned that. The whole reason why the OS still lives as a single entity and the app-ecosystem is not completely fragmented is due to Google's governance to keep it in check.

All the stuff Apple now slowly starts to allow on iOS due to EU's Digital Markets Act is still just scratching the surface of what Android already supports.

> hell, Apple are the only platform now with third party APIs for RCS in the EU

They provide third party API's to use APPLE's RCS-Service. The alternative would have been to support registering alternative RCS-services as default on the OS (and then, allow the user to choose a service).

> while Google’s spun an about face and will get away with it

Android already allows to install and configure alternative applications for RCS, in fact Samsung uses their own RCS Messaging service on its devices.

▲

kotaKat 8 days ago | parent | next [-]

> Samsung uses their own RCS Messaging service on its devices

No? They’ve switched to Google Messages, and most/all carriers have switched to Google Jibe RCS (again, Google forcing its services into operator hands), which basically forces SafetyNet attestation to use.

▲

rickdeckard 8 days ago | parent [-]

Sorry, you're right. I stand corrected, Samsung discontinued their own RCS-Service in January 2025. Yet the point stands, Google doesn't restrict usage of alternative RCS-services on its devices, Apple does.

> again, Google forcing its services into operator hands

Frankly no. Carriers tried to make RCS work and failed for many years. I was involved in so many meetings, individual projects, interoperability testfests, just to make all the crazy "flavors" of RCS required from different operators work with each other. Each of the large carriers thought he could do RCS better than the next one, destroying simplicity, reliability, interoperability.

Many of them rolled out their own RCS-service initially, with flaky UX and ridiculous limitations making it weaker than WhatsApp at that time.

Google didn't start this mess, and didn't force itself into this matter. But yes, they ended it by acquiring Jibe and unifying the platform.

	▲	baybal2 7 days ago \| parent [-]
		[dead]

▲

evan_a_a 8 days ago | parent | prev [-]

>They provide third party API's to use APPLE's RCS-Service. The alternative would have been to support registering alternative RCS-services as default on the OS (and then, allow the user to choose a service).

RCS messaging is carrier-controlled and configured via carrier bundles in iOS. Apple doesn't run a "RCS service". TelephonyMessageKit [0] in iOS 26+ exposes a standard interface to the carrier SMS, MMS, and RCS services, as applicable, allowing for 3rd party applications to send and receive carrier standards-based messages.

In 3GPP standards, RCS is just another service using the IP Multimedia Subsystem (IMS) framework. Carriers can either run their own RCS service in their IMS core or use a 3rd party service (as many do with Google's Jibe).

[0]: https://developer.apple.com/documentation/telephonymessaging...