CCMI was the carriers coming together to form an alliance for a common RCS based on UP. They wanted ownership of the messaging client instead of Google. They were going to use 3rd party backend from Synchronoss instead of Jibe. Even though Jibe would still be compatible they didn’t want Google to own any part of it. T-Mobile was first to enable cross network support via interconnection with Jibe.How do you figure CCMI would sidestep Google? Doesn’t all RCS work with all other RCS’s including Google’s? So, this wouldn’t have sidestepped Google, they’d have been right there in it. AND, still not a single page presented that’s from the GSMA… which has zero interest in RCS.
They abandoned that plan and decided to go with Google.The CCMI was launched in 2019 and by all indications was a joint effort that was spearheaded by Sprint. It initially seemed like a mixed bag of news. At the time, any effort by carriers to support proper cross-compatibility in RCS was a good sign. But the bad part was the consortium planned on creating an Android app themselves for messaging features. If you’ve ever used an app designed by a major US carrier, you know that’s a recipe for a bad experience.
Google was not part of the CCMI announcement, either, which was very strange given that Google is by far the biggest booster for the standard.