I find crowd-sourced anything very compelling. Is there any methodology for getting users? Is there some reliable way to differentiate between "I haven't yet tried hard enough to get users," and "I'm pretty confident this is simply not going to catch on"?
I'm fortunate to be in a position where I can run this forever whether or not it achieves meaningful scale. It's built for me (though it already has resonated with many).
As far as growth is concerned, it's already growing organically on its own and for the time being that's satisfactory to me. I haven't get invested serious resources in growth. Then again, I managed to grow my last product to > 50,000 users purely through and invitation model, with almost nothing spent on marketing. There's a pretty compelling reason IMO to want to build sets together, and I think a lot of the same invite driven mechanics will apply.
That being said, I'm more focused on just building a great product that I use daily.
Also, I think that ~3 months of stagnation, low engagement, lots of "testing this out" sets, I should have a pretty good sense that I'm not going about this in a way that is interesting to others. (But as long as it is to me, then I'm happy.)
Awesome job with this Kyle. I assume you are going to open an API for this later on? I've been wanting to do a project for a while based around this type of information and this would be a great tool to use to get started on it.
12 comments
[ 2.7 ms ] story [ 16.8 ms ] threadWhat advantage does this have over similar services?
"I built it for me" was exact same decision path that I used for delicious.
I have wanted for a long time to revamp delicious's predecessor with ways to nicely present groups of things. So I guess I'm in the same set.
I think it'll do well.
I find crowd-sourced anything very compelling. Is there any methodology for getting users? Is there some reliable way to differentiate between "I haven't yet tried hard enough to get users," and "I'm pretty confident this is simply not going to catch on"?
I'm fortunate to be in a position where I can run this forever whether or not it achieves meaningful scale. It's built for me (though it already has resonated with many).
As far as growth is concerned, it's already growing organically on its own and for the time being that's satisfactory to me. I haven't get invested serious resources in growth. Then again, I managed to grow my last product to > 50,000 users purely through and invitation model, with almost nothing spent on marketing. There's a pretty compelling reason IMO to want to build sets together, and I think a lot of the same invite driven mechanics will apply.
That being said, I'm more focused on just building a great product that I use daily.