Apple will require app devs to explain why they use certain APIs

In the developer documentation it mentions that the restricted activities involving UserDefaults involve writing data that other apps can read, or reading other app's data in UserDefaults. It seems odd to me that if this is a security or privacy issue it couldn't be addressed by a technical means, like preventing UserDefaults from reading from other app's data at all, rather than having every developer that wants to store preference data pinky promise that they won't performed the proscribed actions.

I'm not looking forward to any increase in the amount of nonsense I must deal with to develop for iOS. They seem to have a some kind of garbage boilerplate lower limit that they feel giving us macros and SwiftData has put in danger.