Here's our answer to YC app on the chicken & egg issue:
Our idea does face a chicken-and-egg problem although not in the typical sense.
The 2 groups of users on Chance are Influencers (chickens) & Followers (eggs).
Since Chance is built on top of Twitter - a Follower is able tweet video requests to any Influencer through the Chance app, even if that Influencer has never used Chance before.
Through these Follower requests, the entrance of even just a handful of Influencers (chickens) into Chance has the potential to pull in 100s or even 1000s more Followers into Chance (eggs).
So our strategy initially will be to focus on getting:
A) Followers to request a chance with any of their Influencers already on Twitter.
B) To get pre-subscribed Influencers to broadcast/tweet their availability on Chance, which would immediately pull their followers in.
Its built on an opensource project form github https://github.com/nevir/groc , The application logic is written in django, Celery processes the queue of generating documentation.
Here's our answer to YC app on the chicken & egg issue:
Our idea does face a chicken-and-egg problem although not in the typical sense.
The 2 groups of users on Chance are Influencers (chickens) & Followers (eggs).
Since Chance is built on top of Twitter - a Follower is able tweet video requests to any Influencer through the Chance app, even if that Influencer has never used Chance before.
Through these Follower requests, the entrance of even just a handful of Influencers (chickens) into Chance has the potential to pull in 100s or even 1000s more Followers into Chance (eggs).
So our strategy initially will be to focus on getting: A) Followers to request a chance with any of their Influencers already on Twitter. B) To get pre-subscribed Influencers to broadcast/tweet their availability on Chance, which would immediately pull their followers in.