(Cr)app - Quality Vs. Profit
appicurious.com
appicurious.com
By improving the quality of the product I don't mean fixing bugs, I mean improving UX for example, execution speed, and the sort.
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.
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.
If you need help or just some notes on your project get in touch. I'm always happy to lend a hand if I can.
Cheers
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.
Picking the right value to hit will depend on your market, your users, and your resources.
I especially love:
"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"