I'm developing a windows-based desktop application and intend to make all the source code on github public with anopen-source license, but at the same time I'm brainstorming ideas to potentially make it remunerative (the initial MVP is already plenty usable but it could turn into a very long lived project) with a patreon/subscription model and something that goes beyond a simple donation button. Some of my ideas were:
- Distribute the releases publicly and notify users when a new version is available to download, but implement a more friction-less auto-updated mechanism for subscribers (this would require the user to "log in with patreon" in the app, which is not a problem since most of the app functionality relies on the user being online but could introduce some friction for individuals without a patreon account)
- Could distribute the source code only alongside build instructions, and have the compiled executables locked behind the subscriber wall, but I think it would greatly impact initial adoption
- Delay public releases of the application a couple weeks behind a "subscribers only" fast track which can get the latest version/release early (I've seen this approach used by a couple creators, such as the Cemu emulator)
- As I'll try to create a discord community around the product, can provide subscribers' discord accounts with privileges and access to exclusive channels for priority technical support and features request