Right, the issue is that we are owning our stuff less and less. You used to be able to even buy a copy of an OS on a CD. Thus, I don't think a subscription justifies the cost of maintenance, and a lot of app models don't do subscriptions for app updates.
Of course, if there is a cloud component, that's a different story because there are recurring costs to hosting a server. Or maybe a user uses the service enough to justify the subscription (e.g. Apple Music subscription vs paying per song on iTunes or how Claude Code and Codex are actual subscriptions that are extremely worth it for the user).
I still have my CD for Office 97 and (somewhere) SuSE Linux 7.2, but I can't honestly say I can continue to use those.
The way to get around that is either continually releasing feature upgrades with one-time payments, or paying for access to the software only while you need that access.
Both models have strengths, one is not inherently evil and the other inherently good.
It's easy to say app updates should be bundled into the one-time cost but even that needs to have a time bound on it. When software lasted 3 years that potentially made sense, but now the release velocity is so much higher that there would be an explosion in complexity to try to keep up with all "one-time" releases going back for years.
Even completely Free software packages struggle with the balance with how far back to claim prior releases are under maintenance (e.g. LTS is popular, but so are 'rolling releases'). That's because of the underlying economic complexity with the costs to maintain what has gone before vs. the cost to develop what will come next.
> I like subscriptions because, in the worst kind of corporate management speak, subscriptions align our interests. You pay for the app for the duration that you see fit.
We see the same pattern over and over again: (1) subscription service starts and operates at a loss, (2) people recognise this and sign-up, (3) the service gradually enshittifies to the point where there is no real value propisition, (4) company banks on having enough customers from 1 and 2 that enough people will put up with 3 that they can remain profitable.
I subscribe to a couple of apps (OnX, Strong) and some news sites (Tangle, local sports site); as far as I know none of them started on 1, and 3 hasn't happened yet for any of them. They all provide services that I think are valuable, at a fair price - a price that, as far as I can recall, hasn't changed for any of them in the 4-6 years I've been a subscriber.
In my experience the only genre of HN comments is that subscriptions are evil, so I'm glad to see there are other perspectives. While it's true that software has been around a long time, it's also true that the world changes and building software in 2026 is much different than even in 2012 let alone 1995.
A growing problem is that there are whole generations of younger people who have no lived experience with or imagination about certain benefits we used to have, so the world you're describing is all they effectively know. It's so easy to fall for the midwit take that the past could not have actually been better in some ways, that it's only nostalgia when people claim it was.
> One great genre of HN comment is where people insist subscriptions are the only way a software business can work,
It's the primary way most SW can work. Pre-subscription, you needed to make SW that was so much in demand that it could survive piracy. Once the worry about piracy went away, a lot more SW became commercially viable.
Even Sid Meier said in his memoir that while he hates subscription, the one time they released something on a subscription based the profits were significantly more than selling his games (but he went back to one time pricing on principle).
> I’m honestly not sure what that means. You can’t take Cal.ai and Flighty out of your phone and put them on your shelf. These things are only going to work as long as they’re maintained and updated. It’s not 1995 anymore.
Yeah, that's a big problem I have with modern technology. It's true that there are classes of applications which need constant updates and backend infrastructure. However, there is a huge category of applications which don't need those constant updates and are perfectly functional without constant updates.
For example, a large number of games from the 90s and 00s are still fun to play, you can still play them with friends over the internet by directly connecting. The developers don't need to invest into those games, they are done. They might have bugs, but that doesn't really matter. In fact, constant updates is something that I don't even really desire.
The problem with the subscription model is that it's quite expensive and the entire reason it exists is to try and get users who forget about that subscription (and it encourages businesses to make canceling the subscriptions as hard as possible). It's the gym membership model.
The other problem with the subscription model is that it needlessly kills off software when either the developer loses interest or goes bankrupt.
"Ownership" is something only the HN set cares about. The reason your average person hates app subscriptions the author relegated to a footnote: they mostly exist to trick you into paying for the app more than once.
Folks pay for all sorts of subscriptions, nobody cares about ownership, but when my mom finds out she's been paying $0.99/mo for a "countdown timer" app she used a few times over a year ago she swears off paying for apps for good.
Speaking about paying for apps in general, I'm all for it. The moment a new app shows an ad, if this app seems useful to me, I'll go make a purchase if it's a single "remove ads" IAP with a reasonable price, where "reasonable" is a price that is less or equal to a price of a cup of flat white where I live.
But I really don't see a reason to pay for a subscription for the app I probably don't use that often. If it's impossible to use the app without signing up for a trial, I'll normally set a reminder to cancel it a day before its expiration.
You can cancel immediately and still get that initial trial/month! I always do this, especially for apps i aspirationally purchase a subscription for a year for (fitness/language apps).
Yeah as a rule I cancel every service immediately after payment. If I still need it in the second month I'll just buy another month, it takes seconds and I don't need to track anything. (Only exception being a music subscription, the only thing I use on a daily permanent basis.)
I would much prefer if all services offered an option to buy only one period rather than always requiring manual deactivation - but I also understand they make a lot of money from people paying for things they aren't using.
This is such a garbage take. Yes, if you're running a cloud-backed service, a subscription makes sense. But the overwhelming number of complaints have been when previous download-only apps (e.g. Photoshop) become part of a subscription service (Creative Cloud). And people complain when the option of a thing that didn't need the cloud (like a garage door opener) now is only available in a subscription model (see "Unauthorized Bread" by Cory Doctorow). It's called "enshitification".
I agree 100%. The key thing is that the monthly subscription should be cheap. That way it really does work for everyone - the user does not end up paying very much over a lifetime and they are getting value for it. And I think in most cases the subscriptions are cheap enough because those that aren't get no business. Of course there are rip-offs out there, and there's nothing wrong with them existing, but just don't subscribe to them.
For some reason the floor price is $5 a month when given the complexity of the app and the benefit to my life, the price should be between a few cents and a dollar at the high end.
> Upgrade pricing also doesn’t solve this. [...] versioned upgrades incentivize developers to chase shiny features that people might pay for rather than improving their app and building for the long haul. It makes the product worse.
In my mind this is missing the point. I am very pro-upgrade pricing because upgrade pricing actually forces the developer to think about what their users actually will pay for, or what improvements will make my workflow better, instead of just adding whatever fancy side-quest thing that you've decided I need today.
If users are asking for shiny new features and are willing to pay for them then fine. If we want refinements and are willing to pay for them then fine. If you want to optionally provide backend storage or backups or whatever then fine.
However, if my continued use of a specific version of your software has no continued cost to you, then be absolutely assured that I do not feel a moral obligation to keep on paying for it endlessly, nor should you assume that I do.
> Maybe for budgeting purposes you don’t want to lock in future obligations. And I guess I can understand that, but I can’t help feeling like you have in mind that this one-time purchase is going to be $5 total. And I’m here to tell you that’s not happening. For anything that takes effort it’s going to be more like $200.
Except he's forgetting that before subscriptions, most consumer SW cost $10-50 with a certain timeframe for support. Not every app is Photoshop, you know.
And stuff like music players? Free!
I think the real problem is the ecosystem keeps changing. The need to ensure there is an update after upgrading Android broke the app.
Interesting take. In my gut I hate subscriptions mostly because keeping track of them is annoying. But I’m semi-convinced. I mean, aligning the interests of the developer and the users is a nice benefit.
Something Apple could do is allow iOS to handle some of this stuff automatically. Establish a sort of “small app subscription” account. Keep track of which apps had been opened every month, only pay the subscriptions for the ones I’ve opened, and allow me to set monthly limits. It could also offer feedback to the app developers, “X% of your users didn’t use the app this month,” etc.
> Keep track of which apps had been opened every month, only pay the subscriptions for the ones I’ve opened, and allow me to set monthly limits.
That turns app icons into land-mines though.
Idk what the happy medium is, but there's gotta be something between "buy this kids game once" and "pay $13 a month until he gets sick of it," and I don't think we've quite found one that's equitable for all parties yet.
A difficulty is that making the billing time more granular could reduce the landmine factor, but also would incentivize developers to keep users in the app for longer than necessary. We’ve already seen in social media that that incentive is… quite bad.
Every other business has figured out a way to operate on a single transaction model where I give them money and they give me a product and that is the end of our relationship until I need something else that they make. Somehow we have managed to operate in this manner for hundreds of years. Why is software development any different?
Because your fucking bananas aren't connected to servers in a datacenter that require you to pay monthly bills and engineers need to get paid more than people stacking rocks for living.
It's not. Software subscriptions are a relatively new thing. For a long time before this madness came around, software companies made money hand-over-fist by just selling software in the normal way.
As evidenced by Rent-a-Center and automobile leases there are plenty of non-software businesses that cater to customers who would rather pay a subscription than a one-time transaction.
> Why is software development any different?
I think it's a combination of price-sensitivity and desire for internet-connected features. For example, MS Office 2010 Home was $150 in 2010 (which is ~$230 today due to inflation) and it looks like you can buy subscription-less MS Office 2024 Home for $180. But despite the price coming down in real terms, many people opt for the Microsoft 365 subscription for ~$10/month.
My water heater once emitted a cryptic warning light. I called a local contractor, the person came and spent 10 seconds inspected the appliance, then start dialing the appliance vendor's support number. Support asked him to press some buttons in a fixed sequence and the tiny display on the water heater showed an error code. Support said "yeah, that means part X is not working, but we don't know why" and the solution was replacing that part entirely.
"Wouldn't it be nice if the water heater comes with hundreds of sensors monitoring each part and emit metrics? You can diagnose with historical data and see what was working and at what time which part showed anomaly". As a person doing SRE in my day job, this was what I had in my mind at the time.
No, no, never. Subscriptions never benefit the consumer. They all work exactly the same way:
- Get the user hooked into their ecosystem
- Slowly make the service worse / more expensive / different over time
- The user is paying for a subscription which feels like an investment, so they put up with more crap than they would otherwise.
Trust me. If you have a subscription for something, and you like it, it will change under your feet. It will get worse, and in effect, it will be taken from you.
I'm not paying for the subscriptions. If everyone moves towards subscriptions, I'll move into a shack in the woods. I don't care. I don't want your subscriptions. If you think subscriptions are a good idea I don't want to hear from you, and I wish you had no say in how anything was built.
[edit]
If the counter-point is that mobile apps will suffer, then good. I don't like or any want any mobile apps whatsoever.
I’m with you. I generally refuse. There are way too many things that I’d like to use extremely intermittently that beg for recurring revenue. I just opt out for the most part, aside from a tiny subset of indispensable apps.
As I said in a different thread[0], the fact that some subscriptions are predatory doesn't mean subscriptions are necessarily predatory.
> If you have a subscription for something, and you like it, it will change under your feet. It will get worse, and in effect, it will be taken from you.
Then I can move on and find something else. If I really think I can't, then it's probably providing me with something I find valuable enough to keep. That idea has its limits (again, I don't disagree that subscription services can be predatory) but it's certainly true sometimes.
>If the counter-point is that mobile apps will suffer, then good. I don't like or any want any mobile apps whatsoever.
Right. And if you don't like or want magazines, you shouldn't subscribe to magazines. If you don't like cell phones you shouldn't subscribe to a service. But there's no reason to think that because you personally do not like mobile apps, no one else should like them and no one else can find value in them.
>As I said in a different thread[0], the fact that some subscriptions are predatory doesn't mean subscriptions are necessarily predatory.
"Some" is doing a lot of work in that sentence. Subscriptions are structurally designed to extract payment for non-use. the whole point of the model is to be predatory.
You pre-pay for some allotment of resources but get nothing back for unused resources. And the main profit comes from the gap between what you paid for and the actual usage. And that's just in the best case scenario there the company is not running at a loss just to squeeze you later even harder. The entire model only works if people throw their money into the void.
If a provider genuinely wanted to cover the costs my usage imposes on them, they would bill me for usage. That's the honest version: you used X, here's the bill for X.
Instead, subscriptions deliberately decouple what I pay from what I consume, and they always decouple it in the vendor's favor, never mine. I never (well i think Kagi[0] actually is different, one outlier) get a refund for the month I didn't watch anything or the API calls I didn't make.
>You pre-pay for some allotment of resources but get nothing back for unused resources.
I dunno. This just doesn't quite compute to me as some universal principle.
I paid $30 for a year of Strong (an iOS fitness app), for example. What do you see as the "allotment of resources" there? They're delivering maintenance upgrades and feature releases periodically that I'll use any time I log a workout; the app runs on a phone that I own; the data is presumably sitting on a server of theirs, so it needs to be ready for whenever I want to use it.
I've logged ~40 workouts so far, so let's hope I stay consistent and end up with 80 for the year. That's ~38 cents per workout.
I just don't feel ripped off here, especially since I moved off of a fitness app that I liked less and cost $50/year, the price has stayed the same over four years while improving steadily, and I'm not aware of anything that does what I want for a better price. I'm not sure I'd even want some kind of metering system; psychologically I don't like the idea that I'd have to spend a second thinking about if I want to pay more to log more workouts.
Why does a fitness tracker need continuous development? How on earth is something whose main competition is a $5 notebook and a $1 pen worth $50/yr?
A fitness tracker is exactly the sort of software I would expect to pay once for. It doesn't need some compute-heavy backend. It shouldn't need any backend at all. The entire application is window dressing for a SQLite database.
A pen and notebook do not provide a database of exercises with video instructions; they don't organize/aggregate my data to show records, chart progress over time, and do the 1RM math for me. They don't track my heart rate (via my watch, which live syncs to my phone when desired) and report health data to a service where I like to see it all aggregated. They don't run timers and they don't operate on a platform that can play music, which means they must be an extra thing I carry around and keep track of.
If you think a pen and notebook are the best solution for how you want to track workouts...great! And if you think you could match those features for a lesser cost, post it up and hopefully I'll find it! What I have is certainly not an essential good; one can definitely lift without it. But it provides services that I find worth the cost.
Why is your data stored on their server where they have access to it at any time for any purpose they choose? For that, they should be paying you, no the other way around.
This is a highly suboptimal solution to a problem that doesn't have to exist. If the application as it exists meets my needs, but an update makes it worse, I should be able to keep using the good one.
If I just buy the application rather than license it, it won't change unless I choose for it to by buying the next version. That is ideal.
There are a number of reasons why I avoid software subscriptions, but this is one of the biggest ones.
I agree that this would be a more ideal world to live in (at least as a consumer, dunno about as a producer), but I don't see it as something I can practically choose in 2026 given my mix of computing devices, my priorities, and the computing ecosystem writ large.
I have a couple of apps that I bought in the early days of the App Store that I can no longer use because I didn't think it worthwhile to keep an old iPod Touch running iOS 6 or whatever. I think my Adobe CS license stopped being viable...can't remember actually, if it was the switch to 64-bit or the switch off of Intel that killed it for good.
This problem is doubly worse if you have a family. No one keeps track of their subscriptions. I found out my wife had a NYTimes game subscription she'd forgotten about. She never used it and it cost us an unknown (but likely $100-$200) before we figured it out. Is this the end of the world? No, but we wasted money because these things intentionally obfuscate themselves and received no benefit whatsoever. When was the last time you paid $200 for software? It's been a while for me, but we paid a bunch of money for some stupid subscription that escaped our notice.
I don't get the connection between a subscription and getting a user hooked, making the service worse, or ensure worsening of the service.
All of these things can be true, all without a subscription.
Not having revenue certainly makes it impossible to sustain a business to work on a service, without some other kind of monetization path, like ads, or data harvesting and sale.
Hmm... To my mind, the best way to commercialize software is the old way: pay for the binaries of every major version. This, of course, bars the option of using the software online, and makes pirating it easier, but I think it's the most fair.
This is way too absolute a point. There's services like water and internet service you're effectively subscribed too that don't get worse. There's obvious efficiencies that can be gained from regularizing demand with subscriptions. Amazon Prime is another example of a something I've been subscribed to for over a decade and I don't feel has gotten worse.
For mobile apps? I don't. Mobile apps are generally worse than anything you can get on a real computer. I use as few mobile apps as possible. I certainly don't add additional mobile apps unless there's no other choice. (ie, OTP app from work)
IMO, this whole 'article' has such a corporate bootlicky flavor to it. I pay for subscription (claude, gpt, netflix etc) since there are no real (pragmatic, convenience and financial) alternatives and it's not easy to rig a solution. otherwise the very fact that the only option is app subscription, i stay out of it on principle. even IDApro has perpetual license.
Interesting article, I guess it may come off as a reflection of being of a different mindset than an older style of open source software and culture?
I thought the idea was, software is created with an open source and open license to it - so people know what the software is, and are able to make copies of it freely, and so that becomes hard to monetize.
If you are trying to sell software and make it proprietary with closed source, it's not software you can trust (could contain literally any insecure code) so you avoid it and it would lack people using it (not saying this happens in practice, but I thought was the open source argument).
Hence you're saying, just create / pay for insecure proprietary closed source software that can't be shared and isn't intended to be shared.
The subscription model lends itself towards abuses: namely, you can use something temporarily, then lose access. The open source vision was about creating software that can be freely re-used indefinitely without a required subscription and shared without as much of restrictions.
So I think basically people object to this increased limitation of "indefinite reuses" which you can get with open source software that you "own", and maybe the proprietary closed source tendencies of these locked down subscriptions.
Now granted, some of the newer "spaces" we operate in may look a little differently, with lots of things needing or desiring constant updates and we recognize we only have so much time so a question comes up if we even want or need "indefinite reuse" or to even have open source software or to understand how the software works.
But, there might not even be disagreement here... if you just "donate" to an open source nonprofit project, that could still be framed as a "subscription". I think it's maybe not conventionally how we're referring to subscriptions, but I think I could see your case for reframing the subscription towards being something "good" or "ok".
There are open source monetization strategies, but if code tends towards being less able to be monetized, how can software projects be funded? I think in this "post-intellectual property" open source scenario I'm suggesting at, the funding might shift in other directions (maybe like from selling hardware or tangible physical goods).
But anyway, I guess we would just probably distinguish between "unwanted" and "desired" subscription practices: limited locked down subs versus unlimited maybe subscription-less or limited open source subs.
At least these were some thoughts this essay was generating in me.
Yes open source is a whole different animal, I had a paragraph addressing open source but decided it really needs its own essay, so stay tuned for 'open source is a scam'
The big problem with the subscription model for me is that it gives devs carte blanche to "fix it in post". Its now okay to sell a half baked product and then sell a subscription for bug fixes. Befiore the advent of subscriptions, comapnies sold complete tools that just worked. Im not saying there weren't bugs, but there were certainly far less.
I mean in a perfect world where I knew my subscription fees were going to developers and enabling them to live a high quality of life, sure thing.
Except in practice, that’s rarely the case. The systemic incentives in society have perverted the subscription into little more than rent extraction rather than genuine support. Products see arbitrary “updates” all the time just to justify someone’s promotion or some executive’s whims rather than actual customer feedback or needs. Hiding software behind layers of infrastructure to justify largesse instead of transparency around how it actually works and providing options for those who would rather retain some degree of ownership even at the expense of building the infra themselves.
The entire present-day model for 99% of corps out there isn’t subscriptions-as-support, it’s subscriptions-at-gunpoint. Companies like Panic or Capture One are the exception to the norm, making it clear what the fees actually do and don’t just funnel them up and out to external shareholders.
I am all for supporting developers, content creators, and everyone else involved in technology. I’m just beyond done with forced migrations to new UI/UX or arbitrary monetary extraction schemes for technology that frustrates me rather than helps return time back to me.
Subscriptions are difficult to avoid for certain situations where the developer does a lot of ongoing work and where the work is expected to continue in perpetuity without there being a set-in-stone finished product somewhere in the future.
But in all other cases, or even many of the ones where it is 'necessary', the presence of a subscription is a red flag for predatory pricing. Minor ongoing work or maintenance really doesn't cost as much as the author thinks it does. Keeping the lights on and updating API calls can be covered by new sales of permanent licenses as long as the app continues to sell. But if they had to go with a subscription, the real per-user cost would probably be measured in cents per month. Maybe add a bit more for their profit margin and charge a nice $1/mo. Do you see that anywhere except the rare app by a small developer that doesn't want to price gouge? No, all software businesses want at LEAST $5/10 a month because they've run the numbers and figured out all the tricks to human psychology, and they know they can trick someone into spending 'just $5' without them internalizing that the company is charging them a ridiculous $50-100 per user per year for even the most trivial service, leaving with almost pure profit. This is why investors love anything with a subscription service.
The author just inflates the prices and adds zeros to numbers to make permanent purchasing seem dead in the water, ignoring that we had multiple decades of software development before the advent of subscription services, where those prices were reserved for big professional suites and not your everyday app or a minor service. It's not that expensive, companies charging insane prices has just shifted your perception of what's going on behind the curtain. We even had one-time purchase mobile apps briefly, and they weren't doing it for charity either. Video games that don't require external services are still overwhelmingly priced for a single purchase, and somehow they're making bank despite also having to release updates and bugfixes.
I feel like I'd be more comfortable with subscriptions if accounts weren't consistently required for everything. I don't particularly like everything I do being tied to an email or phone or whatever. And all those accounts are consistently a pain in the butt to delete.
Despite their recent news, I do prefer the way Mullvad has done it re this: "Here's an id. If you make a payment, it funds that id.". Then you can use the id to login. They can still enforce limits like # of users, etc, but it still enables you to have an account where you can be sure the company isn't going to ignore your unsubscribe settings, send you upsells, and then leak your phone # in some db breach.
81 comments
[ 3.4 ms ] story [ 33.8 ms ] threadUnless you mean people are forgetting to use the maximum amount every month, or forgetting to cancel?
Someone should tell the vibe coders because the vast majority posted here seem to include poorly considered subscription plans.
Of course, if there is a cloud component, that's a different story because there are recurring costs to hosting a server. Or maybe a user uses the service enough to justify the subscription (e.g. Apple Music subscription vs paying per song on iTunes or how Claude Code and Codex are actual subscriptions that are extremely worth it for the user).
The way to get around that is either continually releasing feature upgrades with one-time payments, or paying for access to the software only while you need that access.
Both models have strengths, one is not inherently evil and the other inherently good.
It's easy to say app updates should be bundled into the one-time cost but even that needs to have a time bound on it. When software lasted 3 years that potentially made sense, but now the release velocity is so much higher that there would be an explosion in complexity to try to keep up with all "one-time" releases going back for years.
Even completely Free software packages struggle with the balance with how far back to claim prior releases are under maintenance (e.g. LTS is popular, but so are 'rolling releases'). That's because of the underlying economic complexity with the costs to maintain what has gone before vs. the cost to develop what will come next.
We see the same pattern over and over again: (1) subscription service starts and operates at a loss, (2) people recognise this and sign-up, (3) the service gradually enshittifies to the point where there is no real value propisition, (4) company banks on having enough customers from 1 and 2 that enough people will put up with 3 that they can remain profitable.
How does this align with my interests?
I subscribe to a couple of apps (OnX, Strong) and some news sites (Tangle, local sports site); as far as I know none of them started on 1, and 3 hasn't happened yet for any of them. They all provide services that I think are valuable, at a fair price - a price that, as far as I can recall, hasn't changed for any of them in the 4-6 years I've been a subscriber.
It's the primary way most SW can work. Pre-subscription, you needed to make SW that was so much in demand that it could survive piracy. Once the worry about piracy went away, a lot more SW became commercially viable.
Even Sid Meier said in his memoir that while he hates subscription, the one time they released something on a subscription based the profits were significantly more than selling his games (but he went back to one time pricing on principle).
Yeah, that's a big problem I have with modern technology. It's true that there are classes of applications which need constant updates and backend infrastructure. However, there is a huge category of applications which don't need those constant updates and are perfectly functional without constant updates.
For example, a large number of games from the 90s and 00s are still fun to play, you can still play them with friends over the internet by directly connecting. The developers don't need to invest into those games, they are done. They might have bugs, but that doesn't really matter. In fact, constant updates is something that I don't even really desire.
The problem with the subscription model is that it's quite expensive and the entire reason it exists is to try and get users who forget about that subscription (and it encourages businesses to make canceling the subscriptions as hard as possible). It's the gym membership model.
The other problem with the subscription model is that it needlessly kills off software when either the developer loses interest or goes bankrupt.
Folks pay for all sorts of subscriptions, nobody cares about ownership, but when my mom finds out she's been paying $0.99/mo for a "countdown timer" app she used a few times over a year ago she swears off paying for apps for good.
But I really don't see a reason to pay for a subscription for the app I probably don't use that often. If it's impossible to use the app without signing up for a trial, I'll normally set a reminder to cancel it a day before its expiration.
I would much prefer if all services offered an option to buy only one period rather than always requiring manual deactivation - but I also understand they make a lot of money from people paying for things they aren't using.
I am so burnt out of making accounts. verifying my email. entering 2fa. re-logging in. entering cc info. getting spammed with marketing email.
In my mind this is missing the point. I am very pro-upgrade pricing because upgrade pricing actually forces the developer to think about what their users actually will pay for, or what improvements will make my workflow better, instead of just adding whatever fancy side-quest thing that you've decided I need today.
If users are asking for shiny new features and are willing to pay for them then fine. If we want refinements and are willing to pay for them then fine. If you want to optionally provide backend storage or backups or whatever then fine.
However, if my continued use of a specific version of your software has no continued cost to you, then be absolutely assured that I do not feel a moral obligation to keep on paying for it endlessly, nor should you assume that I do.
Except he's forgetting that before subscriptions, most consumer SW cost $10-50 with a certain timeframe for support. Not every app is Photoshop, you know.
And stuff like music players? Free!
I think the real problem is the ecosystem keeps changing. The need to ensure there is an update after upgrading Android broke the app.
Something Apple could do is allow iOS to handle some of this stuff automatically. Establish a sort of “small app subscription” account. Keep track of which apps had been opened every month, only pay the subscriptions for the ones I’ve opened, and allow me to set monthly limits. It could also offer feedback to the app developers, “X% of your users didn’t use the app this month,” etc.
That turns app icons into land-mines though.
Idk what the happy medium is, but there's gotta be something between "buy this kids game once" and "pay $13 a month until he gets sick of it," and I don't think we've quite found one that's equitable for all parties yet.
A difficulty is that making the billing time more granular could reduce the landmine factor, but also would incentivize developers to keep users in the app for longer than necessary. We’ve already seen in social media that that incentive is… quite bad.
It's not. Software subscriptions are a relatively new thing. For a long time before this madness came around, software companies made money hand-over-fist by just selling software in the normal way.
> Why is software development any different?
I think it's a combination of price-sensitivity and desire for internet-connected features. For example, MS Office 2010 Home was $150 in 2010 (which is ~$230 today due to inflation) and it looks like you can buy subscription-less MS Office 2024 Home for $180. But despite the price coming down in real terms, many people opt for the Microsoft 365 subscription for ~$10/month.
"Wouldn't it be nice if the water heater comes with hundreds of sensors monitoring each part and emit metrics? You can diagnose with historical data and see what was working and at what time which part showed anomaly". As a person doing SRE in my day job, this was what I had in my mind at the time.
- Get the user hooked into their ecosystem
- Slowly make the service worse / more expensive / different over time
- The user is paying for a subscription which feels like an investment, so they put up with more crap than they would otherwise.
Trust me. If you have a subscription for something, and you like it, it will change under your feet. It will get worse, and in effect, it will be taken from you.
I'm not paying for the subscriptions. If everyone moves towards subscriptions, I'll move into a shack in the woods. I don't care. I don't want your subscriptions. If you think subscriptions are a good idea I don't want to hear from you, and I wish you had no say in how anything was built.
[edit]
If the counter-point is that mobile apps will suffer, then good. I don't like or any want any mobile apps whatsoever.
"But the subscription is so low!"
We're being nickeled and dimed into poverty.
> If you have a subscription for something, and you like it, it will change under your feet. It will get worse, and in effect, it will be taken from you.
Then I can move on and find something else. If I really think I can't, then it's probably providing me with something I find valuable enough to keep. That idea has its limits (again, I don't disagree that subscription services can be predatory) but it's certainly true sometimes.
>If the counter-point is that mobile apps will suffer, then good. I don't like or any want any mobile apps whatsoever.
Right. And if you don't like or want magazines, you shouldn't subscribe to magazines. If you don't like cell phones you shouldn't subscribe to a service. But there's no reason to think that because you personally do not like mobile apps, no one else should like them and no one else can find value in them.
[0]: https://news.ycombinator.com/item?id=48846637
"Some" is doing a lot of work in that sentence. Subscriptions are structurally designed to extract payment for non-use. the whole point of the model is to be predatory.
You pre-pay for some allotment of resources but get nothing back for unused resources. And the main profit comes from the gap between what you paid for and the actual usage. And that's just in the best case scenario there the company is not running at a loss just to squeeze you later even harder. The entire model only works if people throw their money into the void.
If a provider genuinely wanted to cover the costs my usage imposes on them, they would bill me for usage. That's the honest version: you used X, here's the bill for X. Instead, subscriptions deliberately decouple what I pay from what I consume, and they always decouple it in the vendor's favor, never mine. I never (well i think Kagi[0] actually is different, one outlier) get a refund for the month I didn't watch anything or the API calls I didn't make.
[0]: https://getlago.substack.com/p/why-kagi-launched-no-use-no-p...
I dunno. This just doesn't quite compute to me as some universal principle.
I paid $30 for a year of Strong (an iOS fitness app), for example. What do you see as the "allotment of resources" there? They're delivering maintenance upgrades and feature releases periodically that I'll use any time I log a workout; the app runs on a phone that I own; the data is presumably sitting on a server of theirs, so it needs to be ready for whenever I want to use it.
I've logged ~40 workouts so far, so let's hope I stay consistent and end up with 80 for the year. That's ~38 cents per workout.
I just don't feel ripped off here, especially since I moved off of a fitness app that I liked less and cost $50/year, the price has stayed the same over four years while improving steadily, and I'm not aware of anything that does what I want for a better price. I'm not sure I'd even want some kind of metering system; psychologically I don't like the idea that I'd have to spend a second thinking about if I want to pay more to log more workouts.
A fitness tracker is exactly the sort of software I would expect to pay once for. It doesn't need some compute-heavy backend. It shouldn't need any backend at all. The entire application is window dressing for a SQLite database.
A pen and notebook do not provide a database of exercises with video instructions; they don't organize/aggregate my data to show records, chart progress over time, and do the 1RM math for me. They don't track my heart rate (via my watch, which live syncs to my phone when desired) and report health data to a service where I like to see it all aggregated. They don't run timers and they don't operate on a platform that can play music, which means they must be an extra thing I carry around and keep track of.
If you think a pen and notebook are the best solution for how you want to track workouts...great! And if you think you could match those features for a lesser cost, post it up and hopefully I'll find it! What I have is certainly not an essential good; one can definitely lift without it. But it provides services that I find worth the cost.
This is a highly suboptimal solution to a problem that doesn't have to exist. If the application as it exists meets my needs, but an update makes it worse, I should be able to keep using the good one.
If I just buy the application rather than license it, it won't change unless I choose for it to by buying the next version. That is ideal.
There are a number of reasons why I avoid software subscriptions, but this is one of the biggest ones.
I have a couple of apps that I bought in the early days of the App Store that I can no longer use because I didn't think it worthwhile to keep an old iPod Touch running iOS 6 or whatever. I think my Adobe CS license stopped being viable...can't remember actually, if it was the switch to 64-bit or the switch off of Intel that killed it for good.
All of these things can be true, all without a subscription.
Not having revenue certainly makes it impossible to sustain a business to work on a service, without some other kind of monetization path, like ads, or data harvesting and sale.
> I believe subscriptions for mobile apps are the best thing that has ever happened for both indie developers and iPhone users.
The article isn't extolling the virtue of paying for a utility!
At least when I pay monthly rent my stuff (and usually me) are actually in the unit the whole time.
IMO, this whole 'article' has such a corporate bootlicky flavor to it. I pay for subscription (claude, gpt, netflix etc) since there are no real (pragmatic, convenience and financial) alternatives and it's not easy to rig a solution. otherwise the very fact that the only option is app subscription, i stay out of it on principle. even IDApro has perpetual license.
I thought the idea was, software is created with an open source and open license to it - so people know what the software is, and are able to make copies of it freely, and so that becomes hard to monetize.
If you are trying to sell software and make it proprietary with closed source, it's not software you can trust (could contain literally any insecure code) so you avoid it and it would lack people using it (not saying this happens in practice, but I thought was the open source argument).
Hence you're saying, just create / pay for insecure proprietary closed source software that can't be shared and isn't intended to be shared.
The subscription model lends itself towards abuses: namely, you can use something temporarily, then lose access. The open source vision was about creating software that can be freely re-used indefinitely without a required subscription and shared without as much of restrictions.
So I think basically people object to this increased limitation of "indefinite reuses" which you can get with open source software that you "own", and maybe the proprietary closed source tendencies of these locked down subscriptions.
Now granted, some of the newer "spaces" we operate in may look a little differently, with lots of things needing or desiring constant updates and we recognize we only have so much time so a question comes up if we even want or need "indefinite reuse" or to even have open source software or to understand how the software works.
But, there might not even be disagreement here... if you just "donate" to an open source nonprofit project, that could still be framed as a "subscription". I think it's maybe not conventionally how we're referring to subscriptions, but I think I could see your case for reframing the subscription towards being something "good" or "ok".
There are open source monetization strategies, but if code tends towards being less able to be monetized, how can software projects be funded? I think in this "post-intellectual property" open source scenario I'm suggesting at, the funding might shift in other directions (maybe like from selling hardware or tangible physical goods).
But anyway, I guess we would just probably distinguish between "unwanted" and "desired" subscription practices: limited locked down subs versus unlimited maybe subscription-less or limited open source subs.
At least these were some thoughts this essay was generating in me.
Except in practice, that’s rarely the case. The systemic incentives in society have perverted the subscription into little more than rent extraction rather than genuine support. Products see arbitrary “updates” all the time just to justify someone’s promotion or some executive’s whims rather than actual customer feedback or needs. Hiding software behind layers of infrastructure to justify largesse instead of transparency around how it actually works and providing options for those who would rather retain some degree of ownership even at the expense of building the infra themselves.
The entire present-day model for 99% of corps out there isn’t subscriptions-as-support, it’s subscriptions-at-gunpoint. Companies like Panic or Capture One are the exception to the norm, making it clear what the fees actually do and don’t just funnel them up and out to external shareholders.
I am all for supporting developers, content creators, and everyone else involved in technology. I’m just beyond done with forced migrations to new UI/UX or arbitrary monetary extraction schemes for technology that frustrates me rather than helps return time back to me.
But in all other cases, or even many of the ones where it is 'necessary', the presence of a subscription is a red flag for predatory pricing. Minor ongoing work or maintenance really doesn't cost as much as the author thinks it does. Keeping the lights on and updating API calls can be covered by new sales of permanent licenses as long as the app continues to sell. But if they had to go with a subscription, the real per-user cost would probably be measured in cents per month. Maybe add a bit more for their profit margin and charge a nice $1/mo. Do you see that anywhere except the rare app by a small developer that doesn't want to price gouge? No, all software businesses want at LEAST $5/10 a month because they've run the numbers and figured out all the tricks to human psychology, and they know they can trick someone into spending 'just $5' without them internalizing that the company is charging them a ridiculous $50-100 per user per year for even the most trivial service, leaving with almost pure profit. This is why investors love anything with a subscription service.
The author just inflates the prices and adds zeros to numbers to make permanent purchasing seem dead in the water, ignoring that we had multiple decades of software development before the advent of subscription services, where those prices were reserved for big professional suites and not your everyday app or a minor service. It's not that expensive, companies charging insane prices has just shifted your perception of what's going on behind the curtain. We even had one-time purchase mobile apps briefly, and they weren't doing it for charity either. Video games that don't require external services are still overwhelmingly priced for a single purchase, and somehow they're making bank despite also having to release updates and bugfixes.
Despite their recent news, I do prefer the way Mullvad has done it re this: "Here's an id. If you make a payment, it funds that id.". Then you can use the id to login. They can still enforce limits like # of users, etc, but it still enables you to have an account where you can be sure the company isn't going to ignore your unsubscribe settings, send you upsells, and then leak your phone # in some db breach.