Mac Apps You Buy Once, Not Every Month

At some point the small utility you bought for $8 became $3 a month, and the maths stopped making sense. A menu bar app that converts units does not need a recurring relationship with you. Yet the drift is real, and it’s worth understanding why before deciding what to do about it.

I sell one-time-purchase Mac apps, so I’m not a neutral party here. I’ve tried to make this useful anyway — including the part where subscriptions are sometimes the honest choice.

Why one-time pricing is getting rarer

It isn’t purely greed. Three real forces:

macOS keeps moving. Every autumn brings a new macOS, and apps that touch windows, menus, or system APIs need work to keep functioning. A one-time sale in 2021 funds zero of the 2026 maintenance. Developers who priced for a one-off and then supported it for five years mostly did so at a loss.

The App Store has no upgrade pricing. This is a genuine structural problem. Apple’s store has never supported paid upgrades — you cannot charge existing customers for version 2. So a developer’s options are: ship a whole new app listing and abandon the old one, add a subscription, or work free forever. Many chose the subscription because it was the only mechanism available.

Server costs are real when they exist. An app that syncs, hosts, or calls a paid API has an ongoing bill per user. Charging once for an unbounded ongoing cost is how apps die.

That last point is the useful test. If an app has ongoing costs, a subscription is honest. If it doesn’t, a subscription is a pricing decision. A note-syncing service across five devices: subscription makes sense. A window tiler that runs entirely on your Mac: it doesn’t.

What “buy once” should actually mean

Before paying for anything advertised as a one-time purchase, ask four questions:

1. Are major versions paid upgrades? Many honest developers charge for 1.0 and again for 2.0 years later. That’s fair — and it’s not what “buy once” implies to most buyers. Check the developer’s history: did version 1 owners get version 2?

2. Does it phone home? A one-time purchase that requires a licence server check every launch stops working when that server goes away. The strongest form of “you own it” is an app that never needs the network to run.

3. What happens if the developer stops? For a local, self-contained app, the answer is “it keeps working until macOS breaks it,” which might be years. For anything server-backed, the answer is “it stops.” This is the single biggest practical difference between the models.

4. Is there a trial? Not a refund policy — an actual trial. Direct-download apps usually offer one; App Store apps often can’t.

Where to look for them

A few patterns that reliably turn up one-time pricing:

• Single-purpose menu bar utilities. Small scope, no servers, often one developer. This is where the model survives best.
• Open source with a paid tier. Rectangle is the clean example: the free version is genuinely complete, with a paid Pro if you want more. There’s a rundown of the window managers if that’s your need.
• Long-standing independent developers. Studios like Many Tricks have sold licences for their utilities for years. They tend to charge for major versions, which is the honest version of the model.
• The Mac App Store’s paid-app listings, filtered by “no in-app purchases.” If a listing shows a price and no IAP, there’s no subscription hiding inside it.

The thing to be sceptical of is “lifetime” pricing on a service with real server costs. That promise is only as durable as the company’s runway.

The three I make

Since I’m the author, here they are stated plainly, and you should read this as the disclosure it is:

• Powder Alert — $4.99, once. Snow alerts for 165+ ski resorts from the menu bar. Uses the free Open-Meteo API, no account, no server of mine involved.
• Effunde — $1.99, once. Creates and formats scratch files from the menu bar. Entirely local.
• Staged — free. Arranges all your windows into layouts in one click. Donations accepted from the About window, not required.

All three are native Swift, run entirely on your Mac, and have no accounts and no analytics. I can charge once because none of them cost me anything per user — which is exactly the test I proposed above, applied to my own apps.

The honest caveat

One-time pricing is not automatically the ethical choice, and I’d rather say so than pretend otherwise. An abandoned one-time-purchase app is worse for you than a maintained subscription. If a developer can’t fund the work, the app rots — slowly, then all at once when a macOS release breaks it.

So the thing worth optimizing isn’t “never subscribe.” It’s this: does the price match the shape of the cost? Ongoing service, ongoing price. Local tool that runs on your machine and costs the developer nothing per user, one price. When those line up, both sides get a fair deal, and the app is still there in three years.