Comment on Nothing Phone builds a blue bubble iMessage bridge while Google and Apple fight over RCS
gregorum@lemm.ee 10 months agoApple’s ideology behind not expanding iMessage to other platforms has been - at least in part - due to the security of the iMessage platform and how it authorizes senders and recipients. Apparently, Apple has low confidence in the diaspora of Android devices and just decided to forget even trying to create a client for Android it could tie down to hardware authentication due to not having a reliable hardware base. This was many years ago.
I don’t know if this is still true or even necessary today, or if they’ve even bothered to explore it recently, but that’s Apple’s main issue. Sure, it also benefits them in other ways such as driving users to their platforms, but this is their main issue.
Jakeroxs@sh.itjust.works 10 months ago
Not according to the leaked emails… x.com/TechEmails/status/1589450766506692609?s=20
gregorum@lemm.ee 10 months ago
Clearly they also saw the benefits of keeping it to Apples platforms, but that doesn’t remove the technical limitations, at least, early on.
Like I said, I don’t know if those limitations still exist. Clearly, the profit motive would if it weren’t for all of the legal and regulatory liabilities that exist abroad. This is why I suggested in another comment that purchasing this compatibility layer would be a good workaround for them in that regard.
Jakeroxs@sh.itjust.works 10 months ago
The limitation was added after the fact anyway, like I mentioned in my edit, secure enclave wasn’t added until the A7 chip, which was first used in the iPhone 5S in 2013, two years after iMessage became available.
gregorum@lemm.ee 10 months ago
Although true, it was added to make iMessage (and every other service) more secure, not just as some sneaky way to keep iMessages off android devices.