24 ms·

First of all, congrats! That's awesome :) I would follow startup framework and try to think about what an MVP would be just to test and make sure people would

First of all, congrats! That's awesome :) I would follow startup framework and try to think about what an MVP would be just to test and make sure people would really, actually pay for this instead of just taking their word for it. I had a similar situation with my project (matchist) where freelance developers were really excited about the idea, so my partner and I put our heads down, built it and then realized we spent way too much time building and not enough time getting feedback all along the way and making something much much more basic.

helen842000 14y ago
Thanks! Maybe I have skipped a step going straight to the so-called 'final' design. I need to cut it down to its most basic parts and see if I get feedback on that. If I get positive feedback on just the raw functions that would be motivating!
wpietri 14y ago
Yes, yes, yes! The number of possible products one can make from an initial idea is very large. Some of those products will be great; some ok; most will fail. (Look, for example, at the ocean of to-do lists in your favorite app store.) Most of the information needed do build a great product resides in the world and in the heads of future customers. Releasing early and often is the best way to test the many hypotheses that are generated while creating a product. It also lets you probe the equally important market space. What are people willing to pay for? How much will they pay? Who are those people? How do you present your product? How can you help them engage their friends? As a developer, I'd rather just go build the thing in my head. But that would be the product that satisfies me, not my future customers.