> There is, however, a scenario where leaving a side project to die is not okay: when you make money from it. I disagree. The key factor is not the money, but

> There is, however, a scenario where leaving a side project to die is not okay: when you make money from it. I disagree. The key factor is not the money, but the promise (whether expressly stated or obviously implied). I'm 1000x more upset about a "free forever" service balking than an app politely going dark or charging for a major version upgrade. There's an obligation to honor guarantees and remaining time on billed subscriptions, to be clear about supported OS versions (e.g. unfair to break on 10.11 if you list 10.7+), to assist customers with exporting their data when you retire, etc. Do not make yourself a slave. If the project is a money-sink, be honest about raising rates, cutting features, or shutting down. If the passion is gone, be honest about passing the torch or going dark. There will always be haters, but trust that most people will understand (though silently), and that you also have a very important obligation to support and maintain yourself.