While Apple should adopt RCS, I cannot help but feel that Google is being extremely hypocritical. They complain about iMessage being proprietary, but their implementation of RCS isn’t open source, and I believe they even mentioned they have no plans to open it up for 3rd party devs to implement it into their own sms apps. This just feels like an iMessage equivalent for Android. It has rich features that are exclusive to Android as a platform (more specifically exclusive to Google Messages or whatever the app is called now)… just like iMessage within iOS/MacOS/iPadOS..
Porgey
joined 1 year ago
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.