The Indie Mac Developer's Guide to Pricing in 2026

Pricing is the lever indie Mac developers tweak least and agonise over most. There is no single right number, but there is a structured way to think about it. This is a guide to pricing an indie Mac app in 2026 — the models, the tiers, and the traps.

One-time purchase vs subscription

This is the decision everything else hangs off, and the honest deciding factor is your ongoing cost per customer.

If each active user costs you real money every month — server compute, hosted AI inference, storage, a sync backend — a one-time purchase is a slow leak. You take one payment and then pay to serve that customer indefinitely. A subscription matches your revenue to your cost.

If your app is largely self-contained — it runs on the user’s Mac, your ongoing cost per user is close to zero — a one-time purchase is viable and customers love it. Mac users have a real soft spot for “buy it once.” The classic structure here is one-time purchase plus paid major upgrades: version 3 is a fresh purchase at a discount for existing owners. That funds continued development without a subscription.

The reflexive “subscriptions are just better” is half-true. They are better when your costs are ongoing. When they are not, a subscription can feel like rent for software that does not change much — and that resentment shows up in reviews and churn. Match the model to the cost.

Tiered pricing

Most apps benefit from more than one price point, because customers genuinely differ. A solo user and a ten-person team are not the same buyer, and one price serves one of them badly.

A structure that works well for Mac apps:

• Personal — one person, their two or three devices.
• Household / extended — more devices, for families or an individual with many machines.
• Team — a seat-based tier for organisations, priced per seat or in bands.

Two or three tiers lets customers self-select without a research project. Differentiate them on things customers can immediately evaluate — device count is the cleanest, since it maps directly to “how many of us / how many Macs.” Feature-gated tiers work too, but only gate features that genuinely belong to a heavier user; gating something basic behind the top tier just annoys everyone below it.

Mechanically, tiers are mostly a device activation limit plus a feature set. Personal allows 2-3 activations, household more, team scales with seats — the device activation model does the enforcement.

Lifetime deals: use with care

A lifetime deal — pay once, use forever, no upgrade fees ever — is tempting, especially at launch. It raises a burst of cash and creates urgency.

But understand what you are selling: you are capping the lifetime value of every customer who takes one. They will never pay you again, however long they use the app or however much it costs you to keep serving them. If your costs scale with active users, a popular lifetime deal can quietly turn into a liability — a growing base of customers who cost money and generate none.

Lifetime deals make sense as a bounded launch push — a limited number, a limited window — or for apps with genuinely near-zero ongoing cost per user. They are dangerous as a permanent option on a product whose costs grow with its success. If you run one, cap it.

Pricing that scales with your audience

The last principle: pick a structure that does not need to be torn up when the app succeeds.

That means a model whose mechanics already have room to grow. A signed license that carries a plan and a device limit can express personal, household, and team from day one — adding a tier is a new configuration, not a new system. Pricing built on infrastructure with that flexibility lets you start simple and add tiers, upgrades, and team plans as you learn, without re-plumbing licensing each time. The licensing-at-scale post covers why that headroom matters.

Concretely: launch with a model that fits your cost structure, one or two tiers, and a clear price. Watch what customers ask for. Add tiers and upgrade paths as real demand appears. Avoid permanent lifetime deals unless your costs justify them.

There is no universal right price — but there is a right process: match the model to your costs, keep tiers few and legible, treat lifetime deals as a tactic not a default, and build on licensing that can grow. If you have a pricing experiment worth sharing, send us your feedback.