Is RCS an open standard? I’ve seen some people say it is and others it isn’t and now I’m very confused. Can you please give me a definitive answer?
Is RCS an open standard? I’ve seen some people say it is and others it isn’t and now I’m very confused. Can you please give me a definitive answer?
Yes and no.
You don’t need to make your own OS, but you do need to implement support for the RCS protocol within your app, rather than piggyback on Googles APIs.
I don’t like it, but there’s no legal requirement for google to provide those APIs, like they did with SMS etc.
That’s fair but that also means their “RCS” is really just a name they slapped on their latest proprietary messaging platform.
We know they’ve been trying to get ahead in the messenger game for many years, now maybe they figured if they use the RCS angle it might get some traction.
Or maybe I’m completely off, who knows. Google’s approach to messaging has always baffled me. They could have had a ton of traction and market share by now if they’d have just stuck with one. Why they keep tearing them down and building another one, and why they think this latest one will do any better, I have no idea.
You can interoperate with googles RCS.
If you are willing and able to enter a partnership like Samsung, you can do it fully (including encryption support etc).
Google are determined to not make it easy, and I agree with you, it appears to be yet another messaging land grab.
Trying to put myself in their headspace for a moment, one justification for making it hard is to stop thousands of apps coming out declaring “full RCS support!” through the APIs, then screwing the pooch (through poor security or deliberate back doors or or or).
Right now Google are desperately attempting to make RCS happen, after almost a decade of trying and failing to make various carriers play ball.
They do not want any bad press about how feature poor/insecure/slow/buggy it is right now.
https://github.com/Hirohumi/rust-rcs-client
Someone has written an open source RCS client prototype, but it has been only tested in China, where carriers do provide their own RCS servers as they are supposed. The author has not tested it with Google’s servers, which are probably blocked in China.
If you want to use SIM card based authentication, you need to have the app installed as a system app. That however is not an option for Google’s servers anyway, since they need to be able to work without carrier co-operation. Google uses SMS based authentication instead.
There does not necessarily need to be anything in Google’s servers that would reject non-Google RCS implementations: the SMS based authentication is defined in the spec, too.
Personally, I would not want the Google’s proprietary implementation to serve an API, but there to be a fully open source client instead.