Ask HN: How would you want (indie) software to be sold?

2 points by curiousmindz 3 years ago | 3 comments

I have been working on an desktop application for the past two years. I expect it to have limited appeal because it targets a niche of power users (I would be happy if I manage to get 10.000 paying users).

What would be the "best" way to sell it? The simplest for me would be to make it a monthly subscription, but I dislike them, especially for my scenario.

Here are my considerations that I struggle to reconcile:

    - WANT: Ideally, users should be able to try the app before buying it.
    - MUST: Once you purchase it, it is yours forever.
    - WANT/MUST: I plan on continuing to improve this app for the years to come. How do I do that sustainably?

By the way, I am thinking of using the Mac App Store and Windows Store to distribute it so I don't have to deal with licensing, anti-piracy, etc. However, they might not be flexible enough to enable all these scenarios. So, I'm open to alternatives.

curiousmindz 3 years ago |

One idea that I have is to sell every major version (would be cool if I could give a discount to users of previous versions). Then, I could plan about 1 major version per year, while continuing to give bug fixes to the previous version for 2 more years (a core feature of the app is to connect to 3rd parties APIs online so previous versions will break without updates).

I would also want to give early access to the next major version, so the users don't wait up to a year to try some of the new features. My idea is to start selling the next version as soon as the previous one leaves early access.

njhaveri 3 years ago | |

On the Mac App Store, there isn't a practical way to charge for updates. You could release entirely new apps, but then upgrading is a pain for users, and you lose your ranking and reviews -- and it's difficult to charge an upgrade fee. You can gate-keep features with In-App-Purchases the way Agenda does, but then you're giving away bug fixes and polish on the app for free forever, and that's probably 80% of your development time. Plus, I would imagine the upgrade rate on that model is pretty low, since most users won't care about fringe features being added.

If you really want to offer perpetual licenses with paid updates, since you're a desktop app, you can roll your own licensing system and use FastSpring/Paddle/etc. It's a fair model, but it's a lot of work. It may be worth it depending on your audience - e.g. developers tend to care a lot about this stuff.

Selling this as a subscription is probably the best path if you can stomach the initial ire of users that don't like that model. Depending on your price point, you could consider a 4x-5x multiplier for a lifetime option if you want to try and keep some of them. Yes, you will lose some users that might have paid for a major version, but you'll probably make that up with the recurring revenue from less price-sensitive users.

Best of luck. I know this can be agonizing and there's no easy answer here.

curiousmindz 3 years ago | | |

Thank you for your detailed suggestions. I have a couple more months to make a decision, so I will continue to do some research.

I see that you are also working on a desktop app and have the same concern.

Good luck :)