Many apps start with a one-time purchase. Clear deal. You pay once, you own the features.
At some point, the business model changes: subscriptions are introduced, and features people already paid for disappear or become locked behind a new paywall.
I understand why subscriptions exist. Recurring revenue makes products easier to sustain.
But from a user perspective, this feels like changing the rules after the fact. Not a price increase for new users — but a retroactive change for existing ones.
I recently added GPX import to a project I work on, specifically to avoid data lock-in. The idea was simple: even if someone stops using the app, their data should remain usable elsewhere.
This raised a broader question for me:
• Is it ever acceptable to change the deal for existing users? • Where is the line between sustainable monetization and broken trust? • How do you think about “ownership” in software you paid for once?
Genuinely interested in perspectives from founders and users.
JohnFen•1h ago
If this happens, trust is immediately broken. They have taken away something I paid for. It's a kind of theft.
> Is it ever acceptable to change the deal for existing users?
Not for one-time sales. If it's an ongoing contractual arrangement, like a rental or service subscription, then it's acceptable to change the offer when the contract renews or on terms agreed to in the contract.
> Where is the line between sustainable monetization and broken trust?
There is no tension between those two things. If you make promises, don't break them and there won't be trust issues.
> How do you think about “ownership” in software you paid for once?
If I have paid for software without the terms being a rental from the start, then my expectation is that I will be able to continue to use the software forever (or as long as I have machines that can run it).
I don't expect to get free updates. If I want an updated version, I expect to pay for it. There's a gray area here about security updates, though. A good company will provide security updates at no charge, and feature updates separately for a charge.
skicoachapp•1h ago
Especially the distinction between: paying once to own a version vs paying for an ongoing service.
I think a lot of conflict comes from companies blurring that line after users have already built habits and trust.
The point about security updates vs feature updates is interesting too — that gray area is where many products struggle to be explicit.
JohnFen•53m ago