3 ms·
I am always disappointed at the lack of effort put into discussing what "launch early" really means. For example, let's say you're making a Word Processor[0]. S
by moron4hire 9y ago
I am always disappointed at the lack of effort put into discussing what "launch early" really means. For example, let's say you're making a Word Processor[0]. Surely, putting up nothing more than a download page where people can Stripe their $10 for a copy is not sufficient. There must be a lot more to the story, because there are a lot of projects that have done just that and have gone nowhere.
It's always made to sound like you can "just launch now". But there must be some sort of apparatus in place to promote the product and take advantage of the attention given to the product. Constructing this apparatus must be a significant undertaking, or else more people would do it. So one can't "just" launch. There is still significant work to do up front, it just might not necessarily be programming of your product.
[0] Just for example. Call it, "consumer-oriented software", rather than any sort of SaaS or open-source library or any other sort of software offering.
- nathan_f77 9y agoI agree that it's certainly possible to launch too early, especially if your product doesn't exist, or it's full of bugs and unusable. But this is still good advice for me. I'm just about to launch a service, and I think I've already gone way beyond "MVP" status. I was even planning on doing a big redesign of the whole product, but now I've decided not to do that, because it works fine as it is. I could easily keep working on this product for another 6 months before I was comfortable launching it, but now I think I'm going to set a deadline for early next week, and only work on the most important things.
- staticelf 9y agoWhat is the product? You should always link to your product if possible when you're talking about it. It got me interested even if I just want to take a look.