Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Google's version of RCS on Android is a proprietary closed source fork of RCS that Google refuses to provide a public API for.

> Google's version of RCS—the one promoted on the website with Google-exclusive features like optional encryption—is definitely proprietary, by the way.

If this is supposed to be a standard, there's no way for a third-party to use Google's RCS APIs right now. Some messaging apps, like Beeper, have asked Google about integrating RCS and were told there's no public RCS API and no plans to build one.

If you want to implement RCS, you'll need to run the messages through some kind of service, and who provides that server? It will probably be Google.

So the pitch for Apple to adopt RCS isn't just this public-good nonsense about making texts with Android users better; it's also about running Apple's messages through Google servers. Google profits in both server fees and data acquisition.

https://arstechnica.com/gadgets/2022/08/new-google-site-begs...

SMS is a universal standard supported by even the oldest devices that will still connect to current cellular networks.



To be fair, I don't think Apple has opened up iMessage either, otherwise this problem would have solved itself already with a third-party app.


Apple has never claimed that iMessage is open.

It's Google that goes on about RCS being an "open standard" when their implementation of RCS is anything but.

It's kind of like going on forever about Android being open source before making sure most of the modern APIs are proprietary closed source code you only get with Google Play.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: