- cross-posted to:
- android@lemmy.world
- cross-posted to:
- android@lemmy.world
Samsung has released a new video in support of Google’s #GetTheMessage campaign which calls for Apple to adopt RCS or “Rich Communication Services,” the cross-platform protocol pitched as a successor to SMS that adopts many of the features found in modern messaging apps… like Apple’s own iMessage.
Yeah, the only issue is that RCS is actually better and the counter argument is that Apple is breaking the messaging platform by not implementing it in some way.
The other point to make here is that iMessage wouldn’t have to just disappear. They could continue to support iMessage while just allowing text messages to be better for those who just don’t want an iPhone. The whole thing is hypocritical on both sides. Apple has convinced it’s users, very successfully might I add, that it is an Android problem and instead of having choice over your phone, you should just buy an iPhone.
As someone who works in IT this is really not the answer users should get. To me, this is equivalent to, “your computer quit working? Just buy a new one.” But imagine you only had one choice and it’s because that company refuses to just improve standard text messaging for all users across the board but iPhone users don’t understand that Google has a method to fix this problem Apple just refuses to make it a better experience for everyone.
Additionally, I think RCS is an open platform. Google’s fork of it carries encryption and group messaging integration. Point being Google genuinely has a viable iMessage solution to non iMessage texts. Apple wouldn’t even have to stop using iMesaage.
While I agree, Apple is being obnoxiously stubborn and it truly only does benefit Apple users as well, it just feels disingenuous from Google. It more feels like they want to get their product onto Apple devices. If Apple could implement RCS the way they wanted to and interoperate with Google, then I think it would be a more valid argument (and I suppose they can, but Apple would be caught dead investing money into something like that). But Google clearly wants Apple to use their own version and is putting up this annoying ad campaign to mask it. (As far as I know, the standard RCS implementation doesn’t even include E2EE, rather it’s something unique to googles implementation, correct me if I’m wrong). Google uses encryption as a talking point in their ad campaigns and is honestly for me the biggest reason for it to be used in iOS. Otherwise the experience is only marginally better than sms, and I wouldn’t expect Apple to even bother with it. At least with encryption one can challenge Apple‘s stance on being a privacy focused company…
Im also a software engineer and it’s annoying as hell that Apple is stubborn, but from a business perspective, it’s a gold mine for Apple - ecosystem lock-in is just too valuable to them as a company.
Google’s encryption extension is published so anybody could implement it (if you already have enough access to create your own client, like Samsung)
Has apple tried to work with Google on the RCS version? If not, I see everything you’ve written here as an invalid false equivalency
They haven’t really. What they really should do is run their own RCS server and federate and support the e2e extension, but they don’t want to.
The most annoying part is that the imessage encryption protocol is so far behind state of art (same underlying encryption protocol with small RSA keys and no deniability since ~2011 when Signal has been around since 2010 with a better protocol). Meanwhile Google based their encryption extension on the Signal production. It would be a solid security improvement if Apple adopted it.