Depends. If your carrier implements RCS using simple HTTP auth, just download one of the 0 apps that bothered to actually implement RCS. Otherwise, your carrier may have an RCS app with an API. If your carrier doesn’t support RCS, you should probably treat Google’s RCS server the same way you treat WhatsApp, because it’s based on semi-open encryption with semi-open protocols on a closed-source, implementation-specific backend.
If you want Google to add Google Messages RCS to the SMS API, you’ll have to wait until they bother, which is probably “when someone forces them”. RCS is practically unused in the EU, the only place I’ve seen that cares about this kind of stuff, so you’ll have to contact your representatives.
That’ll only work on phones with Messages preinstalled, though, if you downloaded the app through the Play Store, it won’t be able to host any system APIs that truly expose RCS. It may also require a system update if they implement it by porting their RCS client to the Android operating system.
I mean you could but it would essentially be like ProtonMail, where the only private and secure communications would be with other users on the same platform, which would be near-zero. Would it be better? Yes, but not by much. Better off just to use something like Signal or Matrix if you’re trying to convince people to use something different.
the only private and secure communications would be with other users on the same platform, which would be near-zero.
It doesn’t. 3rd party RCS–> iMessage is not anymore private or secure than 3rd party RCS --> Google. All message metadata is stored on Apple’s servers, just like it is on Google’s.
Good. Now when can I use RCS with 3rd party apps?
Depends. If your carrier implements RCS using simple HTTP auth, just download one of the 0 apps that bothered to actually implement RCS. Otherwise, your carrier may have an RCS app with an API. If your carrier doesn’t support RCS, you should probably treat Google’s RCS server the same way you treat WhatsApp, because it’s based on semi-open encryption with semi-open protocols on a closed-source, implementation-specific backend.
If you’re a developer, grab an RCS library and get coding! I’m sure people will be willing to sponsor or even pay for a good RCS app.
If you want Google to add Google Messages RCS to the SMS API, you’ll have to wait until they bother, which is probably “when someone forces them”. RCS is practically unused in the EU, the only place I’ve seen that cares about this kind of stuff, so you’ll have to contact your representatives.
That’ll only work on phones with Messages preinstalled, though, if you downloaded the app through the Play Store, it won’t be able to host any system APIs that truly expose RCS. It may also require a system update if they implement it by porting their RCS client to the Android operating system.
I mean you could but it would essentially be like ProtonMail, where the only private and secure communications would be with other users on the same platform, which would be near-zero. Would it be better? Yes, but not by much. Better off just to use something like Signal or Matrix if you’re trying to convince people to use something different.
RCS will work with iMessage users in iOS 18. I’ve already tried out with beta users and it works fine.
That doesn’t contradict anything I said.
It contradicts your main point.
It doesn’t. 3rd party RCS–> iMessage is not anymore private or secure than 3rd party RCS --> Google. All message metadata is stored on Apple’s servers, just like it is on Google’s.
Are you just going to ignore you ever said there would be near zero users?
You’re an ass. Blocked.
I’m not ignoring anything. There will be near-zero users. I’ve just explained this. I’m not being an ass and you’ve not blocked me.