{"id":20619,"date":"2022-12-02T20:00:20","date_gmt":"2022-12-02T20:00:20","guid":{"rendered":"https:\/\/mailinvest.blog\/index.php\/2022\/12\/02\/google-keeps-trying-to-hammer-on-apple-for-not-adopting-rcs\/"},"modified":"2022-12-02T20:00:20","modified_gmt":"2022-12-02T20:00:20","slug":"google-keeps-trying-to-hammer-on-apple-for-not-adopting-rcs","status":"publish","type":"post","link":"https:\/\/mailinvest.blog\/index.php\/2022\/12\/02\/google-keeps-trying-to-hammer-on-apple-for-not-adopting-rcs\/","title":{"rendered":"Google keeps trying to hammer on Apple for not adopting RCS"},"content":{"rendered":"

<\/a>\n<\/p>\n

\n
\n

Google continues to beg Apple to fix its messaging problem<\/p>\n


\n \"\"\/
\n <\/a>\n <\/div>\n

\n


\n
\n AppleInsider may earn an affiliate commission on purchases made through links on our site.
\n <\/em> \n <\/p>\n<\/div>\n

In a birthday post on Friday, Google continues to court Apple, trying to get it to adopt RCS. It’s still not ready, not a standard, and not something Google is all-in on itself. <\/p>\n

\n

Apple’s products rely on iMessage<\/a> when commuting with other Apple products, then fall back on SMS for everyone else. Google has been aggressively pushing a newer standard called RCS, but it isn’t quite ready<\/a> for primetime. <\/p>\n<\/div>\n

\n

The latest push from Google arrives in the form of a condescending blog post<\/a>. It is nearly the 30th anniversary of the first-ever SMS text, and Google wants Apple to know there’s something newer… again<\/a>. <\/p>\n<\/div>\n

\n

“Most of the mobile world is using RCS, but there is one company that’s dragging its heels,” the blog post reads, alluding to Apple. “But after 30 years of SMS texting, it’s truly time.” <\/p>\n<\/div>\n

Google’s three reasons why<\/h2>\n

<\/p>\n

\n

The post provides three reasons Apple needs to get on board with RCS. However, the reasoning isn’t exactly sound. <\/p>\n<\/div>\n

\n

First, Google cites security thanks to end-to-end encryption. However, it forgets to mention that users have to send messages via the Google Messages app<\/a> for encryption. That, and encryption for group chats is only available to users of the Google Messages beta. <\/p>\n<\/div>\n

\n

Second, Google says RCS enables higher-resolution images, video, and more things like emoji reactions. However, other messaging services like Signal, WeChat, Facebook Messenger, and even iMessage already have these improvements. It is Google’s problem that Android users don’t have the same benefit by default. <\/p>\n<\/div>\n

\n

Finally, Google calls RCS an industry standard. Which it isn’t, not even close. Google hasn’t even adopted RCS<\/a> across all of its disparate messaging platforms. <\/p>\n<\/div>\n

\n

The post also disparages Apple for using SMS as a fallback, despite RCS doing the same. RCS only works over an internet connection, so it will fall back to SMS just like iMessage does when internet strength isn’t good enough. <\/p>\n<\/div>\n

RCS isn’t the answer<\/h2>\n

<\/p>\n

\n

The foundation of this post is the age of SMS \u2014 30 years. While this is an aging standard that needs to be replaced, it is also a universal one that the entire globe benefits from. No matter how embedded RCS, iMessage, or other platforms become, SMS will take a decade or more to phase out completely. <\/p>\n<\/div>\n

\n

There is also a fundamental issue with Apple adopting RCS since it is a direct competing platform with iMessage. Google acts as if RCS is a replacement for SMS, but it isn’t \u2014 it is just another layer on top of it. <\/p>\n<\/div>\n

\n

Apple debuted iMessage as a method to unify messaging across its platforms and take the guesswork away from its users. Google failed to do the same, and is making it Apple’s problem. <\/p>\n<\/div>\n

\n

Hopefully, Google can #GetTheMessage that it isn’t Apple’s job to fix messaging on Android products.<\/p>\n<\/div><\/div>\n