3 ms·
Just to counter all the "launch now" posts - rushing the launch can actually kill your project. If you come out with a half-baked product, you will have an hon
by huhtenberg 19y ago
Just to counter all the "launch now" posts - rushing the launch can actually kill your project.
If you come out with a half-baked product, you will have an honour of making an initial splash. However the majority of your potential user base will not bite, they will make a note to themselves to come back when there's a better version. So all your competition will need to do is produce that version - better looking, more stable, with more features, etc - and you can kiss you chances of grabbing a decent market share goodbye.
In short - never launch things that are not ready. Not to the general public. This greatly diminishes your chances riding a "viral propagation" wave made by a launch announcement. It also tags you as a developer that's OK with releasing (essentially) crap rather than a polished product. If you want to gather a feedback, do closed beta.