Frequently asked questions
Updated · Dmytro Virych
The questions people ask before they buy Build Mac App, and a few they ask afterwards. Answered in terms of what the app does and does not do, not in reassurance.
What do I get?
Access to the private GitHub repository: the Mac app, the site that sells it, the release pipeline, the payment and email integrations, the checks and the agent tooling — the whole of Build Mac App, as source you own a copy of. Updates arrive in the same repository.
Is Build Mac App a subscription?
No. You pay once, and every update to the template is included for as long as it is maintained.
How many apps can I build with it?
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.
What else do I need?
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.
Does it work with AI coding agents?
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.
How do I get access after buying?
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.
Is there a money-back guarantee?
Yes. 14 days from the day you buy, no questions asked. Email hello@buildmac.app. The refund removes your access to the repository.
Does it cover the Mac App Store?
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.
Which payment providers does it support?
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.
Do I need to know Swift and TypeScript?
You should be comfortable reading both. 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.
Which macOS versions do the apps run on?
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.
Who takes the payment?
Creem, the merchant of record. They charge the card, handle sales tax, and are the name on your statement.
Not answered here? Email hello@buildmac.app. A person answers.