You say "polishing", which implies minor details. Could you cut a bunch of stuff, and release next week? The real adventure doesn't start until you've deployed. You might even find out that the polishes don't even matter that much, and something that wasn't even on your roadmap is everything.

Unless your previous experience was as the first engineer at a startup, your previous experience was probably preparing you to iterate on an existing product (late phases of phase 1 or phase 2), or a new product for existing customers. You had a base level of expectations. Previously, you were forced to released a polished version, but you had the resources to do it. In your new capacity, you (probably) don't have that. There's something to be said for just throwing out there a minimum version of the product, and polishing it later. You'll save weeks of wasted effort probably.

Thank you for the tips. :)

Actually the app is online since 1 month. It was necessary to integrate with AWS, test everything in prod and let people play with the product. I deploy new commits every day.

When I said "I'm polishing for the release", I was referring to:

- make a minimal website to present the product (right now I don't even have a white page but a "Could not resolve host")

- finish to integrate the payment system

- fix some bugs I don't want to have for the public release

One of the best comment i had read regarding launching. Lots of people often under-estimate our past experiences here. Almost all of the s/w job teaches us to release a bug free, polished version . But to launch a side project, you need to overcome your urge to release a polished version, and launch a barely working version to get feedback and iterate. It is one of the major reason of mine to never release a side project till now !

If you release something before it is ready, that'll make a poor impression and the people who try it may never return.