How it works
An installer copies your app’s files to the right place, and on some platforms registers shortcuts, file types or services. Some platforms need very little. A Mac app can be dragged from a disk image to the Applications folder, and a portable build can be a ZIP the customer unpacks anywhere. A formal installer is worth having when you need to write outside the app folder, install a driver, or ask for administrator rights once.
Formats by platform
| Platform | Common formats | Notes |
|---|---|---|
| macOS | .dmg disk image, .pkg installer package, .zip with an app |
Apple’s notary service accepts disk images, signed flat packages and ZIP archives |
| Windows | .exe setup program, .msi Windows Installer, .msix packaged app |
Microsoft’s list of Authenticode-signable files includes .msi and .msix |
| Linux | AppImage, .deb, .rpm, .tar.gz |
A single AppImage file runs without installation; packages go through the system package manager |
| Plugins and extensions | A ZIP, or a store’s own format | WordPress-style plugins ship as a ZIP |
Sign every installer you can: see code signing. On macOS, notarize and staple too (notarization).
Keep license keys out of the installer
A key inside the installer file means one build per buyer, and anyone who passes the file on passes the key with it. Ship one installer for everyone and have the app ask for the key at first launch, then call activate. The same file also serves trial users. A worked example: with 1,000 buyers, a build per buyer is 1,000 files to produce, sign and notarize, and 1,000 files to store.
Installer versus updater
The installer runs once, outside the app. An auto-update mechanism runs inside the app and fetches later versions. If both exist, keep them consistent: the update should install over what the installer put there and keep the stored license and device activation intact.
How Clavem handles it
A Clavem release is a version with notes and one or more files. Each file can be up to 5 GiB and carries an optional platform label, such as macos or windows, of up to 40 characters. The list is not fixed, and a file without a label is offered to every platform.
Buyers download from their order page, which lists the latest published release. Links are signed and expire after one hour, downloads support byte ranges so interrupted ones resume, and files are served as attachments under the name you uploaded. Your app can ask for the latest release by product id and platform:
curl "https://clavem.io/v1/releases/75/latest?platform=macos" \
-H "X-License-Key: YOUR-LICENSE-KEY"
The documented example returns Inkwell-3.2.1.dmg, 50,540,748 bytes, about 48 MiB, so around 20 builds of that size fit in the Free plan’s 1 GB of file storage. Clavem does not build, sign or notarize installers. It delivers the one you upload. Details are in releases and downloads, and the purchase-to-download flow is in delivering software downloads after payment.
Questions
Should the license key be inside the installer?
No. One installer serves every buyer, and keys belong to individual buyers. Have the app ask for the key on first run and activate it.
Is an installer the same as an updater?
No. The installer does the first install. An updater runs inside the installed app and replaces it with a newer version. They are often built separately.