Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
Ask HN: When do you say "enough is enough" and just ship it?
2 points by ghc on July 24, 2012 | hide | past | favorite | 2 comments
I've been developing my first web startup (foldr.co) since winning a startup competition in late February, and while I've made a huge amount of progress, I have an ever-growing list of "must-have" features and design changes that come from interviews with alpha testers and potential users.

I know I should launch as soon as possible, but I'm also keenly aware that any drastic changes to design or functionality might upset users. I'm experiencing an incredible amount of anxiety on this front...so much so that I opened registration to make myself feel like I had "half-launched". How those of you with experience launching startups convince yourselves it's time to temporarily stop development and ship?



Does it do something? Anything? Then the time to launch is now - then run like hell to keep up.

Added: I just tried to sign up and it told me my passwords didn't match, and I know they did. Probably should fix that.

But don't add more features. If it has some features, and it doesn't crash, and it lets people use it ...

Launch.


I suppose one benefit of launching is you can't put off fixing known issues like the wrong error message displaying because I disabled signup after posting the question.

I suppose you're right, and you've convinced me to turn signups on again, but there's also a difference between launching the product (as in letting people use it) and Launching the product (as in marketing, user acquisition strategies, etc.). For the most part, it's the second sort of launch I'm worried about. It seems like a huge distraction that takes away from making the product better, and a large time commitment.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: