spillTea

spillTea uses Polygon’s dApp store kit to re-think how dapps are shared on social media. It’s very obvious that we discover lots of new products on social media and influencers, and thought leaders love to talk about what they use and love. spillTea aims to enhance this already existing process with a simple solution.

Anyone can use the spillTea web-app to create a page (spilltea.xyz/< your-name >) and add the dapps you use the most. Then you can simply share this page on your social media, add it to your bios or add it as a link to existing link-in-bios like linktree, bento. You can simply show which dapps are part of your daily routine, and which you love and endorse by just sharing the URL.

To take this a step further, I’m working on couple more enhancements.

Discovery: a discovery page + search to find spillTea links of your favorite thought leaders and people who inspire you to give a great curated browsing experience of dapps. 



Auto-generate spillTea page: Of course, composability and openness are the core of web3 and I’m going to leverage that to smoothen the spillTea experience further. Soon, you can just connect your wallet and auto-generate a list of dapps you used based on your wallet history. You can then edit it further by putting them into buckets (regular-use, will-endorse, etc...)

spillTea web app is made using React and Next.js leveraging server-side rendering as much as possible to smoothen the experience. The wallet connections are handled by wagmi, and rainbowkit. It’s using the new & mighty SIWE (sign-in-with-ethereum) to sign up users.

The Dapps info, discovery, search and all are handled by Polygon and Meroku’s dApp store kit. It provides a freshly updated list of hundreds of dapps across most EVM chains and I do not need to worry about updating the dapps and their info. This open and central repo of all dapps makes creating discovery and curation solutions like spillTea super easy and does not worry about the mundane data fetching and management tasks.

The backend is powered by JS and a postgreSQL database. I’m going to start thinking of ways to incrementally export all backend to on-chain and to decentralized hosting alternatives.