highlandinfo

I agree -- I'm fortunate enough to be able to consider just buying an M1 mini and sending it to someone in order to support this, but it's not clear who I would send it to, nor if that would even be helpful.

You have not read the guideline carefully or have misinterpreted it; nothing in it locks the end-user into Apple's ecosystem. The requirement is only that if the app uses a third-party authentication system (Facebook, Google, etc.), it must also offer Sign In with Apple alongside it.

You're free to roll your own sign-in system, in which case you are not required to offer Sign In with Apple.

Not seeing a problem here.

Not sure how you'll feel about the EndpointSecurity user-space framework, specifically designed to provide replacement functionality for anti-malware vendors (https://developer.apple.com/documentation/endpointsecurity)...

Developers who are affected by this (and who were on top of last summer's announcements) knew this day was coming, and have been working on updates since then. 10.15 serves as a testbed that supports legacy kernel extensions as well as the new user-space frameworks (e.g. EndpointSecurity and NetworkExtension) that largely replace the deprecated APIs. Developers that have a revision ready to test against the first 10.16 beta this summer should be in good shape (assuming that Apple doesn't swerve wildly between 10.15 and 10.16 cough 64-bit Carbon cough).

Yes, the documentation is scanty in places, and there is some missing functionality at the moment. And the support burden on these companies, once 10.15.4 ships, will be a pain ("It's OK, the software still works, don't worry about that alert message"). But it is incorrect to say that Apple has not given developers time to react.