Replies: 3 comments 6 replies
-
This is definitely very interesting and I can totally see us surfacing this kind of information prominently on the package page 👍 |
Beta Was this translation helpful? Give feedback.
-
It's something we've talked about before this feature existed, and I'm so glad to see Apple tackle it officially! 🎉 I've not looked into them in detail yet but will watch the session video this week and start thinking about the best way to display the data. Is it something you'd be interested in helping contribute? |
Beta Was this translation helpful? Give feedback.
-
@daveverwer @finestructure Just listened to your latest podcast episode where you also mentioned this discussion. One of the things you weren't sure was how to show off the information from the manifest files, so I thought I would share my expectations. The most interesting two bits of info I would like to know are:
My expectation is driven by how Apple groups those labels here: P.S. I'm used to this so no worries at all, but just for future reference, "Jeehut" is how you say my first name "Cihat" correctly. 😉 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm sure you've already had thoughts about this, but I just wanted to raise this topic in case you have not.
Apple this year at WWDC introduced a new feature for SDK authors called "Privacy Manifests", see these notes or the session.
I immediately thought of this project when I saw the video and what I would imagine is a small view summarizing some relevant aspects of the Privacy Manifests that might be important to decide as a developer if we want to include a specific library or not, similar to how the License is also important and presented.
What are your thoughts about this?
Beta Was this translation helpful? Give feedback.
All reactions