The RCS specifications often define a number of options for implementing individual communications features, resulting in challenges in delivering interoperable services between carriers. The RCS specifications aim to define a more specific implementation that promotes standardization and simplify interconnection between carriers.
And if you’re having trouble parsing that, as someone who’s worked with the protocol in the past, no, it doesn’t “go through their servers”, the carriers run their own servers/waypoints, and you’re able to make your own RCS messaging app without touching anything Google-related.
That’s definitely worth considering, but Google doesn’t fully own it, just the initial rec/spec. The carriers need to be fully in on the changes, and Apple picking it up would give Apple a lot of say on the future of it.
It’s mainly Google in the sense that other platforms haven’t picked it up (aside from enthusiast/Linux phone OSes). But it’s there for people to pick up and throw their weight at.
You could’ve at least looked at the Wikipedia page for it before making random claims that make you feel good.
https://en.m.wikipedia.org/wiki/Rich_Communication_Services
And if you’re having trouble parsing that, as someone who’s worked with the protocol in the past, no, it doesn’t “go through their servers”, the carriers run their own servers/waypoints, and you’re able to make your own RCS messaging app without touching anything Google-related.
But it’s still google backed, google developed and google centric. There’s no way Apple will implement a competitors standard.
That’s definitely worth considering, but Google doesn’t fully own it, just the initial rec/spec. The carriers need to be fully in on the changes, and Apple picking it up would give Apple a lot of say on the future of it.
It’s mainly Google in the sense that other platforms haven’t picked it up (aside from enthusiast/Linux phone OSes). But it’s there for people to pick up and throw their weight at.