What ongoing Mac app development actually costs us

SADFinder has a subscription, but it is not subscription-only. You can still pay once and own it.

I want to explain why I prefer the recurring plans anyway — from the engineering side, not with a fake “value journey” diagram.

Shipping the first version was not the expensive part

Recent releases added Dropbox and OneDrive support. Google Drive is implemented, but approval is still pending. We also added 11 themes, Large Text in light and dark, per-folder view settings, better permission handling, crash fixes, and a pile of smaller changes.

That means development time, support time, platform maintenance, and external review costs. A Google Drive audit alone may cost roughly $700.

Then there is acquisition. During launch, I spent more than $55 to acquire a customer who bought the old $30 lifetime license.

The math obviously did not work.

Cry me a river, right?

Fair. But motivation does not pay a developer or an audit bill. If a native Mac app is going to survive OS changes, cloud API changes, bugs, and support requests, the business has to afford maintenance after launch week.

The pricing trade-off

SADFinder now costs:

• $5/month


• $29/year (about $2.42/month)


• $49 once for lifetime access

All three unlock the same app on up to three Macs. The trial lasts 7 days and does not require a card.

Recurring revenue makes recurring work easier to plan. The lifetime option exists because some people simply do not want another subscription, and that is a perfectly reasonable preference.

I wrote the longer version, including the uncomfortable launch math, here:

https://sadfinder.com/blog/why-sadfinder-has-a-subscription?utm_source=devto&utm_medium=organic_content&utm_campaign=subscription_story_2026_07&utm_content=dev_adaptation

For other developers selling desktop software: how are you balancing maintenance costs with subscription fatigue?