The human memory is limited. When you are first excited about something you get lots and lots of fleeting ideas. By the time you are working on the ideas, you have most likely forgotten most of them and then you are stuck. You no longer know what the next incremental step is, even though you feel it should be obvious.
My most successful project was organized via GitHub issues with a title and no content. To start to get into the mindset of shipping all you have to do is gather a bunch of these issues and assign them to a milestone, that is your product, your initial release. It doesn't matter if it is only 1% of the final vision, you will have many more milestones after this one. After your first milestone what you should do is get users. If you can't, then you should stop unless you need the software yourself. If a milestone is too big and you can't finish it in the deadline you gave yourself but you finished a significant amount of issues, then just take some of the issues out and shift them to the next milestone. Shipping will become a regular habit instead of some mysterious event in the far away future.
Solid advice. I also have seen companies not able to follow the simple rules you described, or getting lost in heavyweight frameworks (given that I understand being a single individual vs an entire companies have different problems, my complaint is about underestimating the overhead they create).
Shipping should be a priority, not an afterthought.
how do you get users? i have made apps but fail to get traction. it is after this i lose motivation & will to work on it.
people just dont signup. even tho everyone says its good project.
The human memory is limited. When you are first excited about something you get lots and lots of fleeting ideas. By the time you are working on the ideas, you have most likely forgotten most of them and then you are stuck. You no longer know what the next incremental step is, even though you feel it should be obvious.
My most successful project was organized via GitHub issues with a title and no content. To start to get into the mindset of shipping all you have to do is gather a bunch of these issues and assign them to a milestone, that is your product, your initial release. It doesn't matter if it is only 1% of the final vision, you will have many more milestones after this one. After your first milestone what you should do is get users. If you can't, then you should stop unless you need the software yourself. If a milestone is too big and you can't finish it in the deadline you gave yourself but you finished a significant amount of issues, then just take some of the issues out and shift them to the next milestone. Shipping will become a regular habit instead of some mysterious event in the far away future.