Shipping a MacOS App to the Mac App Store

The Path That Sends a Build to the App Store In Part 1 we created the MAS build target, and in Part 2 we created the configuration files and code branching that separate the two channels. The FocusTimer MAS target is now in a shape that can be put on the App Store. In this final part, we’ll set up the path for uploading that build to App Store Connect, and cover how to verify the two channels so they stay unbroken going forward, wrapping up the series. ...

Making the Target Truly “MAS-Specific” In Part 1, we registered a MAS-only Bundle ID and duplicated the FocusTimer MAS build target. But that target is still just a copy of the direct distribution target. A MAS build has to differ from the direct distribution build in three ways. Entitlements — only the minimum set appropriate for the App Store Info.plist — drop the Sparkle keys, add App Store metadata Code — branch so it compiles even without Sparkle In this post, we’ll split all three. ...

Another Distribution Channel — the Mac App Store The previous series covered the one-time setup for distributing a macOS app directly with a Developer ID. Once you have certificates, notarization, Sparkle automatic updates, and a hosted update feed in place, you can let users download a .dmg file directly without going through the App Store. This series covers the one-time setup for putting that same app on the Mac App Store (MAS) as well. The two distribution methods are not an either/or choice. You can run a single app through both the direct distribution channel and the App Store channel at the same time. The App Store has Apple handle payments, refunds, and search visibility on your behalf, and it carries higher user trust, so running it alongside direct distribution is a common choice. ...