I think it’s a pointless bike shedding exercise to discuss which of your shipping versions was the MVP. I note your mentor is from Google - rather notorious for keeping things in beta long after it’s shipped to millions of users, and killing off viable products because they measure success in billions of users.<p>MVP is about optimising the risk of your investment of effort and money in a new product. It’s not a lagging indicator given by external usage. It’s a decision you make about readiness to launch.<p>Don’t waste time waiting for someone else to tell you that the third version after launch was your MVP. Make the hard decisions about whether you need more design work before launch. After launch, focus on feedback and product fit. Don’t spend time asking “is our already shipping product MVP yet?”<p>(Of course at scale, there are decisions to be made about launching into new markets, integration into other products, how much to spend on marketing, lining up partnerships. All of which may in fact be determined by success to date. But for the product you describe, these are very separate to the MVP conversation you need to have)
To me, the MVP is the minimum demoable product. If it's running, solving a problem and getting feedback, it's viable.<p>The idea is to get something out the door and iterating on that. That started at 0.1.