| > It’s Apples fault SMS is an archaic protocol? Wow, I truly learn something new every day. Why would this only be about SMS? RCS has existed for 15 years. It has its issues, but it’s not as if there hasn’t been an option. Apple will finally add some level of support next year (yikes), but as evidenced by the Beeper brouhaha, it’s unacceptably late to the party. > your complaint is that SMS/MMS is archaic and needs an upgrade No, it’s really not. My complaint is that there’s been an upgrade to SMS/MMS for many years that would make the iMessage limitations irrelevant, but Apple has refused to address the issue. There has been too much focus on iMessage itself, and not enough on the underlying behaviors they’re forcing and the obvious intent behind this. > I guess I just don’t see the argument why iMessage explicitly needs to shoulder the burden here. I honestly don’t care if Apple makes iMessage work on Android. There are numerous options that solve this issue without crossing that line. RCS next year is a step in the right direction. They could also follow their own design philosophy and allow apps to surface their messages in a unified interface like they do for most other iOS capabilities. I can receive a discord call and it shows up next to my normal phone calls. This kind of UX would solve the issue without requiring Apple to touch iMessage. But they won’t, because this isn’t about security or some undue burden to support android devices; it’s a calculated decision to degrade the user experience when messaging non-iPhone devices for the purpose of driving sales. This has even been confirmed by discovery documents from recent lawsuits. |