It would be beneficial to move smart insights into a separate optional package target.
This would permit developers to use the core functionality but not be required to define required reasons for accessing any of the APIs that Apple needs disclosed in the privacy manifest of an app.
While I believe most apps use UserDefaults, there are potentially use cases that don't want the concrete type insight code handlers to even compile and emit into the binary.
It would be beneficial to move smart insights into a separate optional package target.
This would permit developers to use the core functionality but not be required to define required reasons for accessing any of the APIs that Apple needs disclosed in the privacy manifest of an app.
While I believe most apps use UserDefaults, there are potentially use cases that don't want the concrete type insight code handlers to even compile and emit into the binary.