You know I agree with this at so many different levels. I am currently at a point at my App where I need to decide to 'launch' or keep improving the quality of the product.<p>By improving the quality of the product I don't mean fixing bugs, I mean improving UX for example, execution speed, and the sort.<p>We decided on a release on an specific date, and we are sticking with it. But still I think about how much time I should spend improving the quality vs launch.<p>I guess one successful example is delicious. I trashed them so badly for releasing a low quality product (I am referring to the new owners). But then after a week the product already feels so much better than before.So I guess release often, does work.
"Quality counts" is a nice meme, but without specifics it lacks usefulness and can even be misguiding. There are many forms of quality. Some are vital when launching an app, others should be pared back if doing so allows you to launch earlier or provide better core features.<p>The real trade off with Quality is not profit but iteration speed. Every feature you include has a quality scale from 1-10. A '1' is going to be barely usable and will frustrate users, a '10' can take months to achieve and your feature or app may be irrelevant by the time it's done.<p>Picking the right value to hit will depend on your market, your users, and your resources.
A very good read; something I agree with a lot.<p>I especially love:<p>"Start something because you have a passion and you want to create something good and long lasting. Start something because you want to change things for the better"