This post answers the thread earlier today about what to build, how to plan for future users, etc.<p>Again: We at JamLegend call it the minimum valid test. Others call it core features, but it's what you need to get a prototype to market.
So how little should you deliver to users as an first release to get the right balance between getting the great feedback, and not loosing a lot of your initial users because its too simple for their needs?<p>You can either launch too early and it doesn't compare with other more mature services feature wise, or launch too late, and the software is a bit bloated or another service has got a massive lead by introducing one of your main features! (or something along those lines)