Google Messages has one job, but it refuses to do it anymore for many users
phonearena.com
phonearena.com
> Many Google Messages customers have been complaining about not being able to send or receive Rich Communication Services (RCS) messages, and this might be because the responsibility now falls on carriers.
I remember commentators here on HN saying something about Google controlling something about RCS and how they'd want that to be with carriers, and it sounds like now the article is arguing the opposite?
But I agree, that's clickbaity.
Google has quasi-monopolized RCS as a way to fix their haphazard mobile messaging offering. To put weight behind their argument, Jibe was rolled out almost worldwide and enabled for every Android phone running Google Messages. "Look, we have one billion active users".
Once Apple finally caved in, it became harder to hide a proprietary end-to-end solution behind a standard. While MNOs are still using Jibe, they have to support spec compliant IMS provisioning that allows the iOS client to register to Jibe. Some carriers have started migrating Android users to their new registration workflows and associated terms and conditions.
To my knowledge, Google provides P2P messaging for free but there must be conditions. MNOs need to agree on revenue share for A2P messaging, and while I don't know if iOS support will become mandatory, this would make sense from Google's point of view.
This is textbook drug dealer model and it makes sense that a few MNOs won't play along, especially in countries where WhatsApp dominates the market anyway.