Unfortunately, I have to hope this doesn't see widespread adoption. If this becomes the standard it will just add to already existing social pressure to get an iPhone in the US.
replies(6):
All my social circles where we communicate over SMS/RCS group text chats consist of a little gentle ribbing about "those darn green bubble people" and that's about the extent of it. The Android users occasionally respond in kind by showing off some cool new feature that Samsung or Google came up with that Apple hasn't copied yet and everybody laughs it all off.
Meanwhile, we take it for granted that there is a protocol for audio calls and text messages but not for video calls. I would like to more easily video call people with iPhones, and doing so would be technically possible but I can't because Apple benefits from the network effect. If I were to get an iPhone it would not be because Apple did a better job at creating a video call feature, it will be because people I know have iPhones and I want to call them. This seems like it gives incumbents in the space a large advantage because they can compete on having a user base and not on quality.
Ironically, Apple itself developed such a protocol for events and RSVPs (ICS), at a time when they didn't have market dominance. This caught on and it is great. I can make a calendar event in Google Calendar, Outlook, or Apple Calendar and invite anyone from any of those platforms. They can RSVP and I can track their RSVPs and they can also create events in their systems and invite me. This is the kind of thing I like to encourage where possible.
Technically vCal/iCal/ICS (whichever name you prefer) doesn't actually support RSVPs. It isn't in the standards documents. In ancient Microsoft nomenclature that pseudo-standard (de facto standard) for RSVPs is the "Schedule+ protocol" named after an ancient dead predecessor to Outlook's Calendar which originated it. I don't know what Google or Apple call it, and it is such a weird dance of (usually) auto-deleted email messages, so certainly has room for improvement as a protocol.
It would be neat to encourage a new "modern" standard there. Seems like something more web-based (JSON REST API?) than email-based might be a more "natural" API today. (Maybe Apple Invite can help lead the way, I don't know if that's on their TODO list.)
Anyone can have an Apple Account whether or not they own an Apple Device.
In this case, too, you can create Invites on icloud.com on non-Apple devices. Including the webpage seems nicely responsive and can probably make them in an Android Chrome tab if you wanted.
The only remaining obstacle is that it isn't a free feature of an Apple Account, but requires an iCloud+ subscription. But that's useful for Apple Music and Apple TV+ and other products, too, many of which work just fine on non-Apple devices as well.
The US Department of Justice is currently suing Apple for violating those antitrust laws [1]
[1] https://www.theverge.com/24107581/doj-v-apple-antitrust-mono...
Also, GNU/Linux phones exist (Librem 5 is my daily driver). However without Apple's budgets, you can't create the same smooth experience. You just can't compete with the duopoly.
Yes, it does: https://puri.sm/posts/breaking-ground/. Purism tried to created their own smartphone not relying on Apple and Google and it was almost impossible to find the necessary chips. Nobody wanted to share the schematics or open the drivers. People are just locked-in into the duopoly. It's impossible to use popular apps without it, like Whatsapp or even Signal (!).