I found a small recurring charge on my card last month for an app I could not immediately name. It took a minute of scrolling to place it: a menu bar utility I installed for one specific afternoon, used twice, and had apparently been renting ever since for the price of a coffee a month. Not a scandal. Just a small, quiet, repeating goodbye to money I was not thinking about.
That is the thing about subscription software. No single charge is worth an argument. It is the pile of them, each reasonable on its own, that starts to feel like a second rent. My conflict of interest, up front: I make a Mac app, and I sell it the unfashionable way, once, for a fixed price. So weigh what follows accordingly. I am not neutral, but I am trying to be fair.
Subscriptions are not the villain here. The whole question is when.
A rough tally; real totals vary.
The pile nobody adds up
Ask most people what they spend on app subscriptions and they will lowball it, badly. Surveys keep turning up the same gap: people guess a number, then itemize and land near double. A fair share admit to paying for something they have completely forgotten they own. The charges are built to be forgettable: small enough to clear without a thought, spread across enough dates to never land as one alarming total.
Software used to be a purchase, like a hammer. You bought a version, you owned it, and if you wanted the next one you paid to upgrade. Somewhere in the late 2010s a lot of Mac apps changed shape, and some of it was the hammer company realizing it could charge you monthly to keep holding the hammer.
Why makers reach for it
Now the other side, because it is real and I feel it too. Building software is not a one-time cost. macOS ships a new version every autumn and cheerfully breaks things that worked in June. Someone has to test against every beta, chase the deprecated API, and keep the download server up. A one-time purchase asks a developer to do that more or less forever on money collected once.
A subscription fixes that in the most direct way there is: the income arrives at the same rhythm as the work. It funds the maintenance nobody celebrates and lets a small team plan past the next quarter. When TextExpander and others moved to subscriptions years ago and took a wave of anger for it, the developers were less greedy than tired. I have felt the pull at 2am after a system update quietly set the app on fire.
When a subscription is honestly right
Here is the line I have landed on, and it is not subscriptions bad. It is about what you are paying for. If an app runs a service on your behalf, a subscription is the honest structure. Something has to pay for the parts that keep costing money long after you installed it:
- Servers that sync your data across devices.
- A backend that holds your team's shared workspace.
- Cloud storage for the files you keep uploading.
- A model answering your queries on someone else's expensive hardware.
Those costs are real and they recur, so the price recurs to match. Nobody sane expects a company to run infrastructure forever on a single payment from 2019. That is not rent, it is a bill for something genuinely still running.
The test is almost embarrassingly simple. If it just runs on your Mac and phones home to nobody, the ongoing cost it is billing you for is mostly imaginary.
Worth doing once a year. On a Mac, open the App Store, click your name in the bottom corner, and look under Account for your active subscriptions. Then check the ones that bill outside the App Store separately, in your bank or card statement, since those never show up in Apple's list. Most people find at least one charge for something they stopped using months ago. Cancelling it is the best hourly rate you will earn all week.
Stop paying, and the lights go out
The part I cannot make peace with is what happens at the end. Cancel a service subscription and the service stops, which is fair: no servers, no sync, no cloud, because you stopped paying for them. But cancel a subscription to a local tool and many of them reach into your own machine and switch the app off. The thing that ran entirely on your hardware simply stops opening. You never owned a copy; you were renting permission to run software that sat on your own disk the whole time.
That is the move that made subscription a slightly dirty word. Not the monthly charge itself, but the discovery that it was the only thing keeping a local utility alive, and that stopping it left you with an icon that opens to a paywall. A hammer you rent is at least gone when you hand it back. A rented app you can still see, greyed out, taunting you.
Charge once for a tool, monthly for a service
So that is the argument, and it is not radical. Charge a subscription when you run a service, because the cost recurs and sharing it is fair. Charge once when you sell a tool, because it runs on the buyer's machine. Both models are honest. They are just honest about different things.
Which brings me, with the bias I flagged, to my own app. Droppy is a one-time purchase, because it is a tool. It runs on your Mac's own resources and keeps your clipboard and files local. There is no server it needs, so there is no server for you to rent. Paying once is not a marketing angle, it is the price that matches the thing. I keep improving it because the changelog is the promise I made when you paid, not because a meter is running. If you want the longer version, it is one of the principles behind Droppy. You can also earn that lifetime license by showing how you use Droppy. And if the tool is worth it, there is one price to see and then forget.