Skip Navigation

Subscription models for an app that’s not hosting anything is just the dev wanting a constant revenue stream, no matter how they try to word it.

Subscription models only make sense for an app/service that have recurring costs. In the case of Lemmy apps, the instances are the ones with recurring hosting costs, not the apps.

If an app doesn’t have recurring hosting costs, it only makes sense to have one up front payment and then maybe in app purchases to pay for new features going forward

81 comments
  • Ongoing development IS an recurring cost.

    I have zero problem with people trying to get paid for their work, often it is the only feasible way to dedicate enough time to the project.

    I'd prefer open source sure, but I'm not all that opposed to small/individual projects not going that route. Especially when it's not a critical service and there's an abundance of FOSS choices

  • Everyone wants a constant revenue stream, app devs aint unique. And also like everyone else, they charge what people are willing to pay. Price is never about cost.

  • It's no win scenario for developers. While you're ok with "one up front payment and then maybe in app purchases to pay for new features going forward" there's a whole other slew of voices who are going to complain about being nickled and dimed.

    Given those choices (and other factors), as a consumer I prefer the subscription model. If nothing else, it lets me forecast my expenditure and continually re-assess the cost/value proposition of the application in question.

  • This just seems like a Patreon with extra steps. If you like what he does, chip in a bit for it. If not, find something else.

81 comments