Props to you for launching, knowing it's not ready yet and there will be pissed off people because of the bugs. That's a scary thing to do, no matter how easy it is for us all to say we would do it too.
More people need to do this. Like you said, without constant customer feedback, you're tweaking things because you think you should, not because it will improve anything necessarily.
"knowing it's not ready yet and there will be pissed off people because of the bugs."
I realize the conventional wisdom these days is to try to launch something earlier than you want to, but has the goalpost really moved back towards launching products that are "not ready" and full of bugs? I don't know how good or bad the OP's product is, I'm just commenting on the sentiment that its admirable if he did launch something that sucks.
I think there's a certain level of craftmanship and pride in your work that should override the urge to launch early for all the usual reasons echoed on HN. Launching too early can be as disastrous as launching too late, I think this lesson often gets lost in translation because the natural habit is to launch too late.
I'm definitely not condoning purposely launching with a boatload of bugs. Instead, I'm just complimenting the OP on launching knowing that it's not 100% perfect yet and welcoming any positive or negative feedback.
I agree that there is a sweet spot between "too early" and "waiting too long" to launch.
But I think people naturally tend to wait too long, constantly "perfecting" the design, the features, the code, etc, as if to almost ensure they always have something preventing them from launching. Because launching is scary.
More people need to do this. Like you said, without constant customer feedback, you're tweaking things because you think you should, not because it will improve anything necessarily.