It has been less than a week since the our inaugural post and first view of Assembly. We’ve been floored by your response: thank you!
Our original plan was to wait 30 days to see what app idea the community wanted to build first. However, with so much excitement behind all the ideas, especially Support Foo, we couldn’t make the community wait another 3 weeks to get started.
Green-lighting Support Foo
Support Foo is off the leaderboard and the Assembly team is committed to helping everyone build Support Foo into a very successful product. 116 people have already joined the Support Foo team and ready to start building it. Thats 2x the size of the entire engineering department of Support Foo’s biggest competitor!
There are already in-depth discussion WIPs about potential features and a clear MVP from Kevin Hale that we think will make Support Foo really special product. Plus there are already almost 200 early customers in line for Support Foo’s launch.
How to get started making Support Foo
As of today, you can get started and join in building Support Foo. Each contribution you make that to a WIP that is accepted will earn you the points others have assigned to that WIP. When Support Foo ships and starts earning revenue, you’ll get your share of the proceeds based on your stake. You can dig in and read more about how contributions earn you stake if you like or send us any questions.
There are 3 easy ways to get involved and to start contributing to Support Foo:
1. Find a WIP that interests you, work on it, and earn the bounty. Wips range from features that need to be programmed, concepts that need a mockup, design work, or other tasks that help the product improve. You can work on any WIP not tagged with discussion. When you have finished the work, add a comment to the WIP linking to what you created. You’ll earn all the WIP’s points when the core team accepts the contribution.
2. Vote up WIPs you think are important. Voting on WIPs is one way to influence the direction of Support Foo. Wip points prioritize and value the work that is needed to complete the WIP. The more points on a WIP, the more more stake the contributor earns when they complete it. Seeing high bounties of points on WIPs indicates everyone thinks the work is urgent and impactful, therefore those that want to earn more stake in the product are rewarded by working on WIPs with big bounties.
3. Suggest your own WIPs big or small. If you have an idea for the app create a WIP for it and when others agree, they’ll upvote it. Anyone can do the work of the WIP and earn all the points. Sometimes WIPs may be high level discussions so if you see several smaller tasks, don’t be afraid to break up the work in the big WIP into smaller bite-size WIPs.
If you are a developer, you can find the code on GitHub. Referencing a WIP number (e.g. #43) in a pull request adds the its reference to the WIP comments so you can be awarded the WIP by the core team.
Since Support Foo is primarily a web app, we’ve chosen Ruby and the Ruby on Rails framework as the initial tech stack. We picked it because Rails conventions make it easy for a developer familiar them to easily jump in, navigate the code base, and contribute. We're experienced Rails devs so we feel most confident offering help to the community if they're using Rails. Future products that get greenlit will go through a polling phase so the early team members can weigh on their preferred tech stack.
Support Foo is our first product. We’ll kick off development of an additional winning app idea soon and adding some of new ideas to the leaderboard.
We’re improving the platform every day so please send us your feedback. If you have any questions you can email us at [email protected].