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.
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.
Is RCS an open standard?
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?