3 ms·
Has it "failed"? You have a user base, and you've experimented with lots of features very quickly. You now you have a very clear idea of what you want, what th
by 10ren 18y ago
Has it "failed"?
You have a user base, and you've experimented with lots of features very quickly. You now you have a very clear idea of what you want, what the market wants, and a sense of how different features and implementations contribute to that.
Did you have such a clear idea at the beginning? Could have have gotten this clarity in any other way?
Prototyping won't tell you the right way, but it gives you concrete terms to think within: by holding some aspects constant, it's easier to reason about the remaining aspects. Prototyping is an aid to thinking.
But I feel your pain; this is an ordeal. It would be so much less frustrating to know how to do everything perfectly in the first place. :-)
- theBobMcCormick 18y agoAgreed. Releasing early and often didn't fail them. It sounds like they found out a lot about their users, they found out a lot about what their application should really be and how it should really work. They also found out that releasing early and often doesn't mean you have to develop and release every half baked new feature idea as soon as it pops into your head! :-)