1---2name: macos-productization3description: macOS app productization for Swift and SwiftUI apps. Use when preparing or reviewing signing, entitlements, hardened runtime, notarization, packaging, DMG creation, app icons, release notes, installation, Gatekeeper behavior, Sparkle/update distribution, or App Store versus direct distribution.4---56# macOS Productization78## First Pass910- Identify the distribution channel: local development, direct download, enterprise/internal, or App Store.11- Inspect bundle identifiers, signing identity, entitlements, hardened runtime, sandboxing, app icon source, packaging scripts, release artifacts, and install path expectations.12- Read `references/macos-productization-patterns.md` for signing, notarization, packaging, icon, or release-flow work.13- Treat packaging and signing as user-facing product behavior, not an afterthought.1415## Rules1617- Do not claim an app is notarized, signed for distribution, or Gatekeeper-clean unless verified.18- Keep local ad hoc signing distinct from Developer ID signing, App Store signing, and notarized distribution.19- Prefer reproducible packaging scripts over hand-built archives.20- Verify app icons through the current Apple asset pipeline. Do not flatten or simplify assets in a way that breaks platform presentation.21- Keep privileged installs, deletion, and system-wide changes explicit and user-approved.22- Preserve release notes, version numbers, build numbers, and attached artifacts as a coherent release.2324## Validation2526- Run signing inspection, entitlement inspection, and Gatekeeper/notarization checks appropriate to the distribution channel.27- Mount or install packaged artifacts and launch the installed app when packaging changes.28- Verify app icon appearance in the built product, not only source assets.29- Confirm release artifacts match the commit and version being published.
agrim