macos-distribution

To notarize a macOS app for direct distribution, you must use a Developer ID certificate and submit the build to Apple using the `notarytool` command line utility. This process verifies your app against Apple's security guidelines before you create a DMG or pkg installer.

Submitting a macOS app to the App Store requires configuring sandboxing and entitlements, ensuring adherence to Apple's security guidelines, and completing the submission workflow. You must also include a PrivacyInfo.xcprivacy manifest to declare your app's privacy practices.

You can implement in-app purchases and subscriptions in a macOS app by integrating StoreKit. This involves utilizing `SubscriptionOfferView` for promotional offers, managing `Transaction` objects for individual purchases, and using `AppTransaction` to verify the app's purchase state.

Yes, you can support both App Store and direct distribution models simultaneously. This dual strategy requires managing different code signing certificates and configuring your build environment to handle both notarized DMG creation and App Store submission workflows.

Yes, including a PrivacyInfo.xcprivacy manifest is required for macOS app distribution to adhere to Apple's security guidelines. It explicitly declares the types of user data your app collects and the APIs it uses, ensuring compliance before notarization or App Store submission.

Developer ID certificates are used to code sign macOS apps for direct distribution outside the App Store, requiring notarization. App Store certificates are used specifically for signing apps submitted through the App Store submission workflow within a sandboxed environment.