What a productivity app has to get right
People use notes, to-do and writing apps every day, on a phone, a laptop and a desktop. They pay once or monthly, forget the key, switch computers and expect it all to work. Four design choices follow from that.
1. Desktop keys, mobile In-App Purchase
Apple’s guidelines are clear about iPhone and iPad. Under 3.1.1, an app that charges for features or functionality inside the app, including subscriptions, access to premium content or the full version, must use In-App Purchase, and apps may not use their own mechanisms for this, “such as license keys”. So Clavem keys cannot gate paid features in an App Store app on iPhone or iPad.
That splits a multi-platform product into two commercial setups:
| Platform | How it is sold | Licensing |
|---|---|---|
| macOS (direct download), Windows, Linux | Stripe checkout on your site | Clavem key, device limit, signed token |
| iPhone, iPad | App Store In-App Purchase | Apple’s, outside Clavem |
| Mac App Store build | App Store | Apple’s; see macOS apps |
If your app syncs between desktop and mobile, a person who bought on one side needs a sensible state on the other. Decide whether a desktop key also grants mobile features (a business decision plus App Store rules) or whether the mobile app is free to use for synced data and charges separately. Read the guidelines for your category before you promise either.
2. A key is not an account
Clavem has no buyer accounts. A buyer holds a key, an order page link and a device page at /licenses/manage. That is enough to license an app and to let someone free a seat. It is not enough for sync, sharing or login. If your product syncs data, you run accounts: sign-up, sign-in and storage. The license can then be something your account system stores, with the signed token sent to your backend as proof of purchase, as in the AI apps page. Do not make a user create an account just to use a single-device app.
3. A household has several devices
A personal license covers one person’s computers, and people own more than one. A limit of 3 covers a desktop, a laptop and a reinstall. If you sell a family plan, make it a different price with a limit of 5, rather than raising the limit of the single plan. Buyers move: they replace a laptop, wipe a machine and forget to deactivate. Offer a “Deactivate this device” button in the app, and tell buyers about the device page, where they remove a seat with no account and no email round trip.
4. Lost keys are a support load
Daily-use apps have customers who bought a year ago and cannot find the email. Plan for it:
- The order page link in the original email shows the key again. Say so in your receipts and on your help page.
- You can find a license by the buyer’s email in the dashboard or with the management API, and resend it.
- Write a short help article titled “I lost my license key”. The lost keys article has the wording.
Free tier, trial or both
An app people use daily can start as free and upgrade. The usual options:
| Model | How it works | What to build |
|---|---|---|
| Trial | Full app for 14 or 30 days | Start date stored in the app; no license until purchase |
| Freemium | Free forever with limits; paid adds more | A licensed flag; the paid features check it |
| Both | Free tier plus a trial of paid features | Two clocks; more to explain |
For a trial that lives in the app, no Clavem license exists until the buyer pays, so your active license count holds paying customers only. See free trial versus freemium.
Recommended setup
| Setting | Suggested value | Why |
|---|---|---|
| License type | One-time with paid major versions, or a yearly subscription if you run sync | A sync service has running costs to cover |
| Device limit | 3, or 5 for a family plan | Personal computers plus a reinstall |
| Trial | 14 to 30 days in the app | Daily-use apps need time to prove themselves |
| Updates | Releases endpoint for direct builds | Gate downloads on a valid key |
Student and teacher discounts are a Stripe coupon, not a different product. See educational discounts.
Doing this with Clavem
Create a product, connect Stripe, map the price. A buyer gets an email with the key and an order page with the download. The app activates once per device and validates at launch, with the signed token as the offline fallback. Follow the guide for your stack: Swift, Electron, Tauri or Flutter.
Guides to follow
- Device activation in Swift
- Device activation in Flutter
- Offline license verification in Electron
- Software updates in Tauri
Questions
Can an iPhone app be activated with a license key bought on my website?
Not through the App Store. Apple's guidelines say that an app which charges for features or functionality must use In-App Purchase, and that apps may not use their own mechanisms for this, such as license keys. Keep keys for the desktop builds you distribute yourself.
Is a license key the same as a user account?
No. A key proves a purchase and counts devices. It does not log anyone in, sync data or reset a password. If your app syncs, you need accounts of your own, and the key can be one of the things that account holds.