What inspired us to build SimpleAsWater?
Well, it’s no surprise that we were thrilled to hear our name on the stage after 2 sleepless nights and a total of 36 hours of hacking.
Also, thanks to the 12 cans of Monster Energy drinks that kept us alive this whole time.
It was even more exciting for me as it was my FIRST EVER HACKATHON.
We learned a lot of things in those 36 hours.
One of the things that we learned that building apps on Web 3.0(aka Dapps) is much harder than to build an app on Web 2.0(the current web).
So, after the event, we talked and surveyed a lot of other teams on understanding what problems they faced, and we found that there were a lot of different problems that the developers faced.
And this is not just limited to just the hacking teams. The projects on which we built our Dapps also faced a lot of problems when it comes to building and growing a decentralized open-source project.
So, I promised myself to dig deeper into this problem.
And this led me to found SimpleAsWater(a member of Y Combinator Startup School), a community-centered platform that aims to ease building, collaborating, learning, and, discovering stuff on Web 3.0.
Today, I want to share with you what we learned at the hackathon and while building SimpleAsWater.
Making Web 3.0 SimpleAsWater
Making dapps, and open-source projects are hard, which really hinders our ability to get amazing ideas out of mind.
So, What makes building Dapps/Projects hard?
If I want to build a Dapp, there is a big barrier/threshold that I need to overcome. This barrier comes in different forms:
- Shifting to web3 from web2 is hard as it involves a totally different approach of how to build applications.
- It is really hard to find the RIGHT RESOURCES at the RIGHT TIME. Often, the amount of resources is either overwhelming and scattered, or really scarce and under-maintained, which leads you to resources that aren’t useful to you, hence wasting a ton of time. This makes the learning curve much steeper than it actually is.
- As this space(web 3.0) is a bit new, so there are frequent changes and abundancy of broken tools. They work one day and break another day. Often the knowledge of making them work is tribal(closed within the small community) and hidden in some deep issue discussions.
- A lot of times, people tend to compromise to make things just work as they have to learn a lot more if they want to make the Dapp better(reluctance due to the steep learning curve).
A good example of this is building a tic-tac-toe Dapp. Most of the people will just build all the Dapp on-chain(meaning all the compute and memory is harvested from the decentralized ledger). This bloats the system and is highly inefficient. For eg, we can make these Dapps better by shifting some of the logic off-chain, and using IPFS for static storage, etc. But as learning is a big threshold in Web 3.0, PEOPLE TEND TO KILL THEIR CREATIVITY.
- The individual projects(usually new projects) don’t have much incentive to support this cross-project(using different projects within the same dapp) community.
- Thus, individuals have to flock into each project’s closed community to get parts of the answers to build parts of their dapps. And, even if there are a number of individuals who are trying to build similar cross-project dapps, it’s really hard to discover each other.
- New projects(less mature) also have a hard time to keep their documentation up-to-date. This is mostly due to the following reasons:
- As the projects codebase change frequently, it’s harder for them to keep the docs updated.
- Usually, these projects tend to have a small core team, they cannot afford to spend more time on documentation.
- Also as the new projects don’t have any or a good amount of regular open-source contributors, they can’t even outsource the documentation work to anyone interested. Here being a regular contributor is really important as the docs are expected to contain each and every detail of the project, that only a regular contributor can have(in such a frequently changing codebase).
What are the main CAUSES of these PAIN POINTS?
- Lack of a self-supportive cross-project community.
- Lack of a community-sourced knowledge graph.
How can we solve this?
Building a Community which is centered around making it easy to build Dapps and facilitating a cross-project community.
In short, building a community that eases:
- Learning, and
stuff on the Web 3.0 space.
What will the ecosystem become if this works out?
- As we are making it easy to build dapps, this will increase the number of dapps and dapp builders.
- Collaborators will be able to find RIGHT RESOURCES at the RIGHT TIME.
- More projects will survive, grow and get discovered.
- More discovery, lesser REINVENTING the WHEEL.
- It will make individual projects even stronger as now they are a part of a much bigger community.
- THIS IS BEST BENEFIT OF ALL: As we unlock this new highly connected community, we will start to see a new breed of dapps, and a much richer variety of dapps.
How can you help us?
- As a Collaborator(anyone interested in Web 3.0)
- As a Project(any Web 3.0 supportive project)
You can start by telling us about your experience with Web 3.0, HERE :)
You can join us here, and we will add you as a BETA partner, HERE :)
Thanks to Towards blockchain, NuCypher, Kyber Network, Matic, Torus Labs, Jeff Lau, AZTEC team, Aavesome, QuikNode.io, DAOstack for making the event possible.
Thanks to the speakers Vii Sundaram, Anand Venkateswaran, Vitalik Buterin, Nina Breznik, Kartik Talwar, Vignesh Sundaresan, Justin Myles Holmes and many more.
Looking forward to attending more Eth event :)
Thanks for reading ;)
About the Author
Vaibhav Saini is a Co-Founder of TowardsBlockchain, an MIT Cambridge Innovation Center incubated startup.
Want to learn more? Check out my previous articles.
- Understanding IPFS in Depth(1/6): A Beginner to Advanced Guide
- ConsensusPedia: An Encyclopedia of 30+ Consensus Algorithms
- Getting Deep Into Ethereum: How Data Is Stored In Ethereum?
- ContractPedia: An Encyclopedia of 40+ Smart Contract Platforms
- A Beginner’s Ultimate Guide To DAGs
Say hi to me on Twitter: @vasa_develop