Intro
cherry.builders addresses a painpoint that is common to many builders and hackers: "how do I casually find other builders with complementary skillsets?". The key word here is "casually", since the go-to option Fiverr is very formal. Therefore, cherry.builders can be thought of as P2P Fiverr, or Tinder for Builders.
Phases to Date
Lessons Learnt from Hackathon Organisers
🍒 use privy for social login, airstack to prepopulate profiles, mbd to prioritise matching, zkPass for sybil resistance
🍒 useful to incentivise hackers to sign-up early
🍒 filter "I have a project" vs "I'm looking for a project"
🍒 work on algorithm
🍒 ways to verify participants - OTP, event password...
🍒 sponsors often request participant data from hackathon for hiring research
Edge City Lanna Experimentation
Being in Chiang Mai, Thailand, at Edge City Lanna, has allowed us to dive into a fast iterative cycle. For the past week we have been shipping fast, demoing on stage, getting feedback from builders and feeding that back into development. As you can see in our public github repo, we have:
🍒 added privy social login, so users can login with wallet, farcaster, email, google or github.
🍒 secured and future-proofed the site and db, ready to scale both in users (secure) and in code (separation of concerns).
🍒 improved and iterated on ui/ux, based on feedback collected on the ground.
🍒 built an integration with cursive.team , who built the tech in the wristbands of everyone at Edge City Lanna. Now cherry users can verify their attendance at Lanna by tapping their own NFC wristband. Furthermore, in view of the upcoming Lanna hackathon, they can check a filter to only see other Lanna participants.
Loose Roadmap
Our full focus is on product. We will keep iterating to get a product that people really love to use, with our target audience being web3 builders, specifically at pop-up cities and hackathons. We have a loose roadmap that is not fixed: