[pawelwentpawel]

I'd vote for Jon's method of one week code, one week marketing:

- Limiting distractions. I won't get any work done if every five minutes I'm checking notifications that come in as a result of my marketing efforts. It gets me out of the zone immediately.

- It forces a 50/50 split. It's too easy to stick to what you're good at. In my case it's coding and building the product - it's my comfort zone. It gives me a feeling for accomplishment and productivity. Feeling productive while neglecting the other side of the process is dangerous.

- It's enough time to incorporate feedback from users quickly while staying sane without sacrificing the process itself.

As per the release anxiety mentioned by the OP - that's a very common one, especially if you're the one that actually made the product. One way to tackle this is to view it as a continuous process of release, not a single event in the calendar. For me this means building confidence in increasing steps and doing a release often with a smaller audience first (maybe some small subreddit or a submission website?) and gradually increasing it as time goes on. This also allows you to spot any bugs or problems quicker.