RCS for Business
developers.google.com27 points by sshh12 21 hours ago
27 points by sshh12 21 hours ago
It's unfortunate that RCS is basically a de-facto Google walled garden in most countries. On android you can only use RCS in the Google Messages app and trying to build your own is explicitly blocked. [1] And of course the bonus that rooted devices are banned from RCS. All the propaganda Google spread to get Apple onboard (only with Google's blessing of course, Google could kick apple off if they wanted) was such a big win for them.
As a business I wanted RCS to be a simple upgrade to SMS, but instead they came up with this mess. Businesses using RCS for Business can send messages to anyone, but customers wanting to get in touch with your business can't. They can only reply to a message you sent first. And of course Google is the gatekeeper for anyone to be allowed to use it.
> trying to build your own is explicitly blocked
Google doesn't offer an RCS API, but making your own API is not blocked, especially not on phones running MicroG.
For standard ROMs, RCS apps are not feasible because carriers expect interaction with the SIM module, and only privileged apps can do that. Google Messages blocks root access (probably because the RCS spec says they have to if they ever implement the money exchange feature for RCS) but that just locks out Google Messages.
LineageOS, GrapheneOS, /e/, and all the others could build their own RCS client. They may not be able to register with Google, but they can make an RCS app nonetheless. Rooted devices can also promote third party RCS apps to gain system permissions, so they would be able to use the same RCS apps. Thing is, like all telco protocols, RCS is a long spec with a billion features and acronyms made up of acronyms of even more acronyms, plus you can't easily set up your own server (though in theory a sister project for an open RCS server might be useful for the open 5G project).
I get why people want Google to just stuff their RCS library into open source Android the same way they do SMS/MMS, but to say it's impossible to write a client for, especially when running at the permission level MicroG runs at, is not the whole truth.
As for the whole "Google is the gatekeeper" thing: there are more RCS-for-business providers out there. Google's is probably the easiest to use by far, but Twilio has RCS too, as well as smaller companies such as LINK Mobility and Esendex. Sure, the people whose carriers don't support RCS might receive these business messages through Google's servers, but there's no need to pay Google a dime to make use of the RCS for Business specs.
> LineageOS, GrapheneOS, /e/, and all the others could build their own RCS client. They may not be able to register with Google, but they can make an RCS app nonetheless.
Building a spec compliant RCS client for the love of the game, I guess.
> but there's no need to pay Google a dime to make use of the RCS for Business specs.
Assuming we're talking of global RCS and not domestic deployments (China and Korea mostly) you pay Google indirectly in all cases as Jibe is monetized via A2P revenue share.
> customers wanting to get in touch with your business can't Not technically true, though it can be more difficult. It's similar to how Apple Messages for Business works where you have to be given a URL (or QR code) to start a conversation with a business using RCS.
> Businesses using RCS for Business can send messages to anyone, but customers wanting to get in touch with your business can't.
Basically for blasting spam and ads, which RCS is already notorious for.
Ironically this is because of federation; if your carrier just uses Jibe (e.g. if you live in the US) then you don't deal with spam because Google has effective tools and a profit motive.
Also ironic: Google spent a decade forcing the world's carriers onto the worst messaging standard, only to end up where they started with Google Talk and XMPP; they are the only ones with significant market share on the protocol.
to your point i had problems with RCS in an entire organization because you must allow *.goog for rcs to work correctly
What does this incarnation of RCS mean? Relentlessly Cancelled Services?
RCS is basically spam-only messaging at this point. You can enhance your messaging experience by just turning it off.
I get vastly less spam on RCS than I do on SMS or iMessage.
The main thing Apple/Google needs to fix is RCS group messaging where spammers change the name of the group message to "Apple" or the business they're trying to impersonate.
This seems very specific to a few regions, India mostly.
Google is doing a really good job catching and blocking spam as far as I'm concerned. Even scammers aren't trying their luck over RCS in any way significant compared to Telegram, WhatsApp, or even iMessage.
I'm so old and out-of-touch that all I could imagine this was about was an ancient version control system:
I had my family iPhones revert to RCS. We had to delete chats and reset settings and reboot phones to get iMessage connected between these contacts again.
And it’s weird how bad sms messaging on Google Voice is, still. RCS would be welcome.
I'm pretty unclear about how the experience they showcase in the video would work on iOS. Maybe Android has APIs for this, but on iOS it looks like RCS just supports green-bubble messages, links and files/multimedia. But in the demo they show multi-choice cards, carousels, cards with buttons, and reply auto-suggestions.
Also, someone correct me if I'm wrong, but it also looks like this needs to be agent-initiated, ie. you can't add a "Text us" button that will take you to this experience. (But you could capture a phone number, and text them _iff_ they have RCS available and enabled.)
Overall, seems questionable whether this is worth integrating if the experience is so fractured across platforms and many people might not even have RCS. The concept of a platform for rich messaging across platforms sounds good though.
I have never seen any of this in real life.
However, all of this is in the RCS spec. If Apple implements the RCS spec beyond the bare basics, all of this should Just Work.
RCS is much more than just "SMS but via weird HTTP" and things like chatbots and interactive components were one of the selling points towards ISPs to bother supporting it.
Unfortunately, nobody seems to bother dealing with the standard. Now Google is at it again, selling "RCS for business" when the RCS standard itself is supposed to be used in a federated, carrier-to-carrier fashion just like SMS.
I have, on my iPhone, RCS messages from businesses that don’t show up as a green bubble, have (somewhat) interactive components, and exhibit non-standard (also non-intuitive) behavior I didn’t expect of either an RCS or an iMessage.
So I guess they did implement all that.
(Not that they are particularly nicely implemented - the layout and padding is all wrong, alignment is off, and it looks distinctly non-native… but that’s par for the course on iOS 26.)
I did just manage to dig up a source that says these things are somewhat implemented in iOS 18 with illustrative screenshots rather than actuals, and it seems to be implemented but currently janky:
- On iOS, rich cards have a message length limit of 144 characters. (Implies this is not a limitation on Android.)
- On iOS, multi-CTA might fold some of the options away. So you might give 4 options and it renders 2 options and makes you use a drop-down for the others.
- On iOS, carousels display as cards, which might not be as obvious to interact with.
https://www.infobip.com/blog/apple-rcs
Potentially improved in iOS 26. It's a little hard to work out the state of this, and of course not trivial to test without joining some kind of partner ecosystem.
What I think this is: as a reward to themselves for not stopping the tidal wave of fraud and phishing distributed via sms, they're going to charge businesses to message you in verifiable manner. So when your bank, ups/fedex for package delivery, walgreens/cvs for prescriptions, etc want to contact you google is going to charge.
As a reward for helping make sms untrustworthy, they're going to tax trustworthy communications.
So is RCS a Google platform, like how iMessage is an Apple platform? It might theoretically be a GSMA standard, but from their marketing page and how it's implemented in reality, it seems like it's the former.
A bit different in that RCS is available on both iOS and Android (and I guess theoretically other platforms?) while iMessage is strictly Apple devices
RCS is a standard, but it needs hosted services for providers. Providers can either host themselves, or contract with someone like Google Jibe Cloud. Also, Google provides services for Android for providers that don't have it. iPhone depends on the provider so has less coverage.
> Providers can either host themselves
Outside of China, it is de facto a Google thing due to Jibe not really in mood to interconnect with others, plus the fact that Google actually shoehorns RCS in countries where they think they can get away with it. Your statement "iPhone depends on the provider so has less coverage" basically bares this one. Two example:
1. Japan has already a different provider-supported thing +Message, (RCS-based but a different flavor because RCS is complicated), but Google is trying to win to them (and if I remember correctly, au actually jumped ship to Jibe recently-ish).
2. African carriers were confused because of RCS shoehorning without the carrier's consent: SMS reliably actually decreased because Google assumes that once you got an Android phone, surely you won't temporarily use that SIM on a "basic" phone for just an hour or two, right? Google just assumes that's offline, but for people still using their Android devices to reach their family on a farm who temporarily switched to a basic phone for its reliability and reach, their messages will still be send solely via RCS (which predictably won't reach the intended recipient because, of course, it does not have RCS).
Apple of course has its incentive to keep its users on iMessage, but it now accepts RCS (whether Jibe or not) and being "patchy" means that there are many, many carriers which did not implement RCS on their volition. I just imagine how would Google handle an oppressive government's request for interception on Jibe after carriers demonstrably shown that RCS was implemented without their consent, with fines and possibly prison sentences for illegally operating a carrier service to boot.
Re: lawful interception, when carriers switch to IMS registration (as required by Apple) they should also get access to Jibe's standardized API for law enforcement tools (there's a spec for that, I forgot its name). However, just the fact RCS payloads are E2EE in Android-to-Android communications (and soon Android-to-iOS too, hopefully) might already be illegal in some places.
Google flip-flopping around its mobile IM strategy for a decade and then around carriers with RCS is getting harder and harder to understand. Pulling the rug under carriers in developing countries, who weren't interested in the drug dealer marketing tactics, is only going to solidify Meta's dominance, as doing business with WhatsApp has proven to be a much safer and saner bet all along.
It's the same as how Android is technically open but the vast majority of users are getting the Google version.
If RCS is supposed to be an open standard, then how come Google can gatekeep the "for business" bit for themselves?
They don't (https://www.twilio.com/en-us/messaging/channels/rcs, https://www.cm.com/rcs/, https://www.linkmobility.com/en-gb/channels/rcs, https://gatewayapi.com/rcs/, https://www.productsupport.esendex.com/what-is-rcs-messaging..., the list goes on).
Google makes RCS servers for carriers, host RCS themselves for carriers without RCS servers, and builds the most used RCS client app, so it makes sense that they're in the RCS monetization market as well, but you don't need to use them.
Google's pricing being displayed upfront while most others are listed as "contact us" will make Google much more attractive to small apps, of course.
Pretty much because the other major telcos tried to run their own rcs services and did so terribly
TIL they have a rich multimedia API for RCS.
With the quality Google is pushing out these days, I wouldn't touch this with a 100ft pole.