If RCS is supposed to be an open standard, then how come Google can gatekeep the "for business" bit for themselves?

jeroenhd 5 hours ago | parent | next [-]

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.

	▲	dfajgljsldkjag 4 hours ago \| parent [-]
		Twilio, Bandwidth etc. are gatekept by Google and are basically just a middleman reselling Google's product. Every single customer on the planet reachable via "RCS for Business" is through Google's servers and the Google Messages app.

▲

adzm 7 hours ago | parent | prev [-]

Pretty much because the other major telcos tried to run their own rcs services and did so terribly