Ask HN: Review my project, fakebuttons.com
http://www.fakebuttons.com/
The backstory: Last year, I was building a bunch of niche websites. And, I'd think of features I wanted to build. But since I wasn't sure if features I thought were cool were actually cool, I would add fake doors to my site to determine whether or not to fully build out a feature. Since I was building lots of sites, I did this often, and I decided to write some code just for this purpose.
I've now thrown it together quickly on fakebuttons.com so that other developers can test new features before building. It's very bare bones right now but would love any and all feedback. Thanks.
16 comments
[ 3.7 ms ] story [ 36.5 ms ] threadGetting users excited enough about something to click a button and then telling them, "Ha, we haven't implemented that feature yet!" isn't good usability in my book - sorry.
Yeah, I'm still working out the pricing. Good idea on pegging it to page views. Email collection is the ability to collect emails when someone clicks on a fake button. A message will popup and say something like "Thanks for your interest -- add your email to be notified when this is ready."
As a web developer, your hook line "Not sure what features to build?" has my attention. "Add fake buttons to your website to test market demand before you build." has me intrigued. Now I'm looking for "how does this work for me?" and "how does this work for my users?"
In the "Ok, how does this work?" section, it stops before the bit I really want to know. "We'll start measuring user demand for your features." How? I think if you described the experience for users of my site, that would clear things up.