It doesn't matter how good of an interface designer we are, there's nothing more valuable than feedback from real people other than yourself using your application. The sooner that happens, the better off you'll be.
Of course, there's always a risk that the app might be so rough around the edges that people immediately dismiss it. Fortunately, this is easy to solve by slowly phasing people into the beta. Start with friends who are more forgiving and more invested in helping you succeed. Then slowly expand the beta as you feel more comfortable.
The priority of planned features for Sifter has shifted fairly dramatically since opening it up to people that aren't me. I've heard many different perspectives and been inspired to create solutions I could have never envisioned on my own.
Looking back, not finding a way to launch something within the first two months is the single largest mistake I've made with Sifter. It's worked out well, but I definitely wish I could have been getting feedback sooner. It's made a world of difference in helping Sifter evolve to where it is now.
We built a simple bug and issue tracker named Sifter and we blog about it when we're not working on it. We think it’s a great way to get feedback and keep everyone updated on our status.
Grab our feedWe'll only send emails for significant product announcements, and those happen every couple of months at most. Of course, we won't give away or sell your e-mail address either.
Comments
Well written.
Feedback is very hard to obtain as a startup. We recently wrote a post regarding how we arranged for the users to easily send us feedback. We mentioned NextUpdate in this post for doing a very good job with promoting Sifter before lunch.