It's the final 20% that kills so many side projects. I wrote about this a couple of years ago, as I used to hit the same problem with my own projects. https://

It's the final 20% that kills so many side projects. I wrote about this a couple of years ago, as I used to hit the same problem with my own projects. https://medium.com/swlh/5-reasons-your-side-project-never-became-a-product-150216bbab5d https://medium.com/swlh/5-reasons-your-side-project-never-be... I got over it by religiously plotting out the final steps to release, and then ticking them off 1 by 1. I find it useful to give myself an "official release date" and then trim features off the list so that I can meet that date. You need discipline to do this, and you need to be able to look at your app or whatever it is critically, with a user who is not you in mind. You don't need to be in this frame of mind all the time, just in those final weeks as you prepare to go live. The final weeks can be boring to a degree, but as you tick all those dull tasks off the list and near the finish it can get exiting and build up a very real sense of achievement. Of course, none of the above determines whether your app will be successful or not. That's a whole different thing. But if you never release, it absolutely, 100%, will not be successful.