Is building an MVP still about building the minimum product?
by•
I've been thinking about how the definition of MVP is changing. In the past, building an MVP usually meant spending weeks or months creating the smallest version of a product that could test an idea. Now, with AI tools, someone can build a working prototype in days or even hours. But I wonder if the bottleneck has moved: Is the MVP still the product itself? Or is it now the fastest way to test whether users actually care? How much should founders build before talking to customers? I've noticed that it's easier than ever to create something functional, but much harder to know whether you're building the right thing. For founders who have launched MVPs:
What was the biggest lesson you learned from your first version?
11 views
Replies
I think MVP has shifted from “minimum viable product” to “minimum viable learning.”
AI tools like @autocoder.cc make it much easier to build a prototype quickly, but the real challenge is still validating the problem, talking to users, and learning what actually matters.
Building is becoming cheaper — knowing what to build is becoming the real advantage.