Inuk
9to5MacApp Store to require developers to describe why their apps use certain APIs https://9to5mac.com/2023/07/27/app-store-describe-app-api/?utm_source=dlvr.it&utm_medium=mastodon
steve 
@9to5Mac UserDefaults?!?!
Alex Rosenberg@9to5Mac @stroughtonsmith I wonder which social networking app was caught using these things to uniquely identify users and violate their privacy.
So many useful tools are not in the App Store because of those companies. No network scanning tools and now no file browsers, build systems, etc.
Israel Chaves Arbaiza@9to5Mac Now that they'll participate on AI tools, it sounds just like a more disguised way of doing like Within and Microsoft
James Harvey@9to5Mac we have to justify why we want to get the size of a file now???
Mudkip@9to5Mac Why UserDefaults?
Doug Burns@9to5Mac in return, I’d love to have an API that returns a persistent user/device id if I can explain how I’m not using it for nefarious purposes.
Brandon@9to5Mac UserDefaults seems surprising given that it’s seemingly the preferred way to store basic preferences, though I’m fully inclined to move to SwiftData and AppStorage (which I think uses UserDefaults?) where applicable. This is a great change, though; we should be transparent in explaining what data is being persisted or read from disk, and clarity is always welcome over a lack of clarity.
Brian Gerfort🇺🇦
@9to5Mac It seems like the definition of “collect” is pretty important here. Does my app “collect” the file size if that info never leaves the app? Same for settings. This all makes more sense if “collecting” means that info leaves the device and is sent to the developer / 3rd party.