Frequently asked questions

The source code of a finished, working Mac app and the website that sells it, in a private GitHub repository you are invited to. The checkout, licence keys, emails, signing, notarization and automatic updates are already built and wired together; you change the app into yours and connect your own Apple and payment accounts. Updates to Build Mac App arrive in the same repository.

Yes, if you are happy to work with an AI coding agent and follow step-by-step instructions. You describe what your app should do and the agent writes the code; the project’s checks tell it when it broke something. What an agent does not remove: opening an Apple Developer account and a payment account, and reading what it changes before you ship. The step-by-step guide is public, so you can see whether the first stages feel doable before you buy, and there is a 14-day refund if they do not.

No. You pay once, and every update to the template is included for as long as it is maintained.

As many as you like, and you owe nothing further for them: no royalty, no revenue share, no attribution. The licence is for one developer; a colleague who works on the code needs their own.

A Mac with Xcode; an Apple Developer Program membership (a yearly fee paid to Apple) to sign and notarize the app; an account with Creem or Polar to take payments; and somewhere to host the site — it deploys to Vercel as it is.

It is built for them. The repository carries rule books written from real failures, a machine-readable map, a doctor that reports what is left to do, checks that name the file and the fix, and thirteen skills with hooks for Claude Code. Tools that read AGENTS.md get the same rules.

Creem is a merchant of record: the legal seller of each order. It charges the card, calculates, collects and pays the sales tax and VAT owed wherever the buyer lives, and handles invoices and disputes, which Stripe on its own leaves to you. The cards are processed by Stripe underneath, and Creem is the name on the statement. Your app sells through Creem or Polar the same way, and a skill in the repository walks an agent through adding another provider if you prefer one.

Checkout asks for your GitHub username, and GitHub sends you an invitation to the repository within a minute. If you leave the field empty or mistype it, the receipt links to a page where you can name the right account.

Yes. 14 days from the day you buy, no questions asked. Email hello@buildmac.app. The refund removes your access to the repository.

No. It is built for selling directly: a Developer ID-signed, notarized download from your own site, with your own licence keys and updates. That is the path where you keep the customer relationship and choose the payment provider.

Creem and Polar, both merchants of record that handle sales tax, chosen with one setting. A skill walks an agent through adding another provider, and a shared test suite decides whether the result is correct.

You do not need to write them: every stage of the start-here guide comes with a prompt for your agent, and the checks tell it what it broke. You should be comfortable reading what it changes. The app is Swift and SwiftUI, the site is Next.js and TypeScript, and every non-obvious decision is explained in a comment beside the code — which is also what lets an agent make changes safely.

Apps built from it run on macOS 14 Sonoma or later, Apple silicon or Intel, as shipped. The floor is one setting if you need a different one.