When it's time to stop work on a project?
Developers spend a lot of time on their projects. It seems that a little more to refine, change the functionality a little, and then the project will go to the moon. But sometimes it's important to recognize that this project is dead and it's time to forget about this idea.
Tell us about your conditions, with the help of which you understand that the project is dead and you no longer need to continue wasting time on it.
Trending on Indie Hackers
Your SaaS Doesn’t Have a Traffic Problem — It Has a Trust Problem
I Got Shadow-Banned on Reddit So Many Times That I Built RedChecker
If you are not sure whether to continue working on a project or not, it is always best to consult with your supervisor or another experienced individual. There are a few general guidelines that can help you make the decision, however. If you are no longer enjoying the project, or if it is taking up too much of your time without yielding results, it may be time to move on. Additionally, if you find yourself constantly making excuses not to work on the project, it is probably not worth your time and energy.
A project is dead in my opinion after you've made one major iteration on the core engagement model and it is still flawed. After one major iteration, if you're still seeing core, fundamental flaws...you will most likely get to "success" faster if you simply start with a new product idea. This is a gut rule I live by.
@nikitabear
Put all your effort after the deployment into marketing, branding, promotion...
for all it's not the same some projects take much time to show the good result if you have a good idea and you know this project will work, you never quit because you have put your time into it and if you stop then you will start again what about if the new project will not show the result in the start?
I'd give it a month or two after launching to see if you get a paid customer. This is coming from someone who does not have an audience currently.