Jibe is a google owned (bought) cloud service that hosts RCS infrastructure as well as serves as an interconnect to other global RCS Hubs. So not unless you are a Mobile network operator or own a MVNO, I'm not sure what your interest are in Jibe.
I’ve little interest in Jibe other than to explore your assertion that Google has no proprietary implementation of RCS. Apparently it does contrary to your assertion.
The standard is being contributed to by mobile operators and platform holders which Apple and Google are. Apple had every access to the standard and specification as it is being drafted. They didn't have to wait for the specification to be finalized to adopt features.
Apple didn’t have to wait for the specification to be finalized, but what advantage was there for them to do so? iMessage/Messages has served its users well while RCS has been a hellscape of patchy and incompatible carrier support. What other projects would they have to cut to fund an RCS project? I’ve worked on software that has been going through industry-standard revisions. Adopting and implementing proposed changes before they have been accepted is speculative work. It only pays off if you have agreements with others who will use those changes or if you have an interest championing/forcing change.
There really was no benefit for Apple to adopt RCS sooner. As you will admit, it was only recently that carriers in the US started using RCS in an interoperable way. And, in the US at least, that was only due to a persistent lobbying campaign to get them to adopt Jibe, with Verizon only relenting this year. Globally, the implementation is still patchy. Someone on this thread was even complaining that carriers in Australia don’t support it.
Google adopted 2.7 before it was even published, they were beta testing features. Apple has no incentive to; you are forgetting they had to be forced to adopt RCS in the first place.
As has been noted, Google has a service called Jibe which implements RCS support for carriers. Google has economic incentive for them to stay on the leading edge.
We should definitely criticize Apple for actively refusing to adopt RCS and waiting to be forced to adopt it because they wanted to lock people into Apple ecosystem.
No one has been locked into the Apple ecosystem by Messages.
Same thing they did with USB C on iPhones even though they helped create and contributed to the standard.
I think you are out of touch with users. Most Apple users I know were initially upset that Apple switched to USB C. Literally within the week or two I have heard two different comedians make snide jokes about disliking Apple because they keep changing cable connectors. Let’s not forget that lightning predates USB-C by four years. Nor should we forget that people still have USB A devices and get upset at having to buy dongles to use old devices on new machines.
It's not part of the standard but Signal is an open protocol that anyone can adopt. Google published the white paper on how they integrated signal extension on top of RCS. Apple is no stranger in working with Google when it suits them financially to do so.
Still, it was a Google only implementation. If you are arguing that Apple should follow just because Google did something, then you cannot be taken seriously.
GSMA has announced their plans to add MLS protocol to the Universal Profile spec. MLS specifications were fully published last year. Google has already started implementing it in their messaging app. I can criticize Apple a multitrillion dollar corporation for not adopting features that protect their customers messages when they talk all the time about privacy and security. I don't understand your insistence on shielding a multitrillion dollar corporation from being criticized.
Yes, you can criticize Apple for not implementing MLS, even though it is not yet part of a published standard and no one else has implemented it either. You can criticize Apple for “not adopting features that protect their customers messages”, even though Messages has had E2EE since 2011. And you can laud Google, even though it didn’t get around to adding an Android-only non-standard E2EE until 2020. Of course, it all sounds very special pleading and biased.