Would you launch an imperfect V1, or keep polishing before putting it out there?
I've been thinking about this a lot while building our first version.
The product works, and the core experience is there, but there are still some bugs, rough edges, and occasional inconsistencies. Nothing fundamentally broken, but definitely things we already know we could improve.
One side of me thinks we should just launch it, get it in front of real users, and let actual usage tell us what matters. Otherwise, it's very easy to spend weeks fixing things that users may not even care about.
The other side worries that a rough first experience can hurt more than it helps. People might try the product once, hit a bug or see something inconsistent, and never come back, even if the underlying idea is good.
So for founders who have been through this:
Where do you draw the line between "good enough to launch" and "not ready yet"?
Would you rather ship an imperfect V1 and iterate in public, or delay the launch until the experience feels genuinely polished?
Would especially love to hear what you did with your first product and whether you'd make the same decision again.
Replies
Promomix
Break your bugs into two columns:
Friction (Annoying UI, slow speed)
Blockers (Data loss, broken login)
Fix column 2 Ignore column 1 for now.
my team delayed our first app by three months just to clean up minor UI bugs and honestly it was a huge mistake when we finally launched no one cared about those details they wanted features we hadn't even thought of building
Man launch it today You can fix bugs along the way but once time is gone so you cant get it back.
i get the anxiety but have you actually given it to like 5 total strangers to test yet their reation usually gives you the answer instantly.