There are plenty of reasons to be unhappy with Apple's policies, or lack of documentation, or undocumented API changes, or even the dismissive tone they can tak

There are plenty of reasons to be unhappy with Apple's policies, or lack of documentation, or undocumented API changes, or even the dismissive tone they can take when talking about 3rd party developers (especially when defending against various anti-trust inquiries), but that's a very weird thing to be angry about. Apple mandates changes all the time, and mandating Apple ID if you already use 3rd party logins is about the least controversial thing I can think of, and the most uncontroversially pro-privacy, pro-user, with incredibly small drawbacks and requirements feature I can think of. iCloud Private relay comes a close second on real user benefits (there are certainly way more drawbacks for the web at large). At least it's decently documented (try Homekit documentation for a counter point), it's really not a huge job to implement, and there's a clearly stated purpose, force developers to give a "social" sign up that won't harvest their data. That's exactly the kind of leaning on devs that's a 100% win for end users and that I, as a user and dev expects and wants to see from them. Less unannounced/undocumented screen saver api changes please, though, but I wouldn't cry a tear either on a ban on 3rd party "SDKs" that harvest any data. Personally, I think adding a Facebook login to an app is a terrible thing to do, and the excuses of "just because it's convenient for users/will increase my signups" just don't fly with me, but that's just my strongly biased opinion. Ranting (so inaccurately) to your users like that though? I think we can come to a broad consensus that it won't achieve a thing and doesn't exactly will fill your users with confidence about what you do with their data?