Banner Image

All Services

Writing & Translation technical

Google Posts Yet Another Plea for Apple

$5/hr Starting at $25

Google has struggled to get carriers to sign on for RCS, which adds support for features like end-to-end encryption and typing indicators.

Google is making yet another attempt to persuade Apple to support the RCS phone-messaging standard in its own iMessage service, but this time it’s aiming the sales pitch at iPhone users.

At a "Get the Message(Opens in a new window)" site posted Tuesday, Google calls out the least-common-denominator aspect of texts between iPhone and Android users: Everybody loses such features as encryption, typing indicators, and read receipts supported separately by Apple’s iMessage and the Google-backed Rich Communications Services (RCS), also called “chat features” in Android.

“Apple creates these problems when we text each other from iPhones and Android phones, but does nothing to fix it,” the page declares. “Apple turns texts between iPhone and Android into SMS and MMS, out-of-date technologies from the 90s and 00s.”

Subsequent paragraphs emphasize how iPhone users don’t only suffer the indignity of seeing Android-using friends’ messages in green bubbles but also miss features they enjoy in conversations with other iPhone users. For example: “Without read receipts and typing indicators, you can’t know if your Android friends got your text and are responding.”

Privacy also loses out in cross-platform conversations, the page notes: “SMS and MMS don’t support end-to-end encryption, which means those messages are not secure.”


(But while RCS supports end-to-end encryption(Opens in a new window) in one-to-one Android chats, group Android chats today only get encryption in transit, with “e2e” security advertised as coming later this year. Bringing this same security to chats between different apps and different platforms would be much harder.)

Apple has never shipped an iMessage client for Android, and court documents unearthed during Fortnite’s lawsuit against Apple revealed that the Cupertino, Calif., company rejected an iMessage port because it might weaken iMessage’s customer lock-in effect.

Google has instead tried in vain to get Apple to add RCS support to iMessage–most recently, at its I/O developer conference in May. But while this latest sales pitch may win over some iPhone users, Apple has a history of ignoring requests from users that don’t square with its own product


About

$5/hr Ongoing

Download Resume

Google has struggled to get carriers to sign on for RCS, which adds support for features like end-to-end encryption and typing indicators.

Google is making yet another attempt to persuade Apple to support the RCS phone-messaging standard in its own iMessage service, but this time it’s aiming the sales pitch at iPhone users.

At a "Get the Message(Opens in a new window)" site posted Tuesday, Google calls out the least-common-denominator aspect of texts between iPhone and Android users: Everybody loses such features as encryption, typing indicators, and read receipts supported separately by Apple’s iMessage and the Google-backed Rich Communications Services (RCS), also called “chat features” in Android.

“Apple creates these problems when we text each other from iPhones and Android phones, but does nothing to fix it,” the page declares. “Apple turns texts between iPhone and Android into SMS and MMS, out-of-date technologies from the 90s and 00s.”

Subsequent paragraphs emphasize how iPhone users don’t only suffer the indignity of seeing Android-using friends’ messages in green bubbles but also miss features they enjoy in conversations with other iPhone users. For example: “Without read receipts and typing indicators, you can’t know if your Android friends got your text and are responding.”

Privacy also loses out in cross-platform conversations, the page notes: “SMS and MMS don’t support end-to-end encryption, which means those messages are not secure.”


(But while RCS supports end-to-end encryption(Opens in a new window) in one-to-one Android chats, group Android chats today only get encryption in transit, with “e2e” security advertised as coming later this year. Bringing this same security to chats between different apps and different platforms would be much harder.)

Apple has never shipped an iMessage client for Android, and court documents unearthed during Fortnite’s lawsuit against Apple revealed that the Cupertino, Calif., company rejected an iMessage port because it might weaken iMessage’s customer lock-in effect.

Google has instead tried in vain to get Apple to add RCS support to iMessage–most recently, at its I/O developer conference in May. But while this latest sales pitch may win over some iPhone users, Apple has a history of ignoring requests from users that don’t square with its own product


Skills & Expertise

Android DevelopmentApp DevelopmentApple PagesiPhonePhone Support

0 Reviews

This Freelancer has not received any feedback.