2 min read

[BAB] Lesson 6: Resources to help you start building

So, now you know everything you need to do to be ready for mass adoption of your dApps:

  • don't expose your users to gas fees
  • make it easy for people who don't have wallets yet
  • build a community and don't expect to be the center of it
  • avoid centralized points of failure

Simple right? The hardest part starts now. Take your idea and start working on it. Don't be afraid to talk to people about it--everyone has their own ideas to worry about. You'll gain more by talking to people than any risk of people copying your ideas. Besides, copycats are just a signal that you're doing something that matters.

If you don't have an idea you're excited about, I'm currently developing a list of "100 profitable dApp ideas" -- if you're interested, reply with "YES" and I'll send you an advance copy for free.

If you're a full stack or frontend developer, you have most of the skills you need to build your app. There's relatively little work that actually goes into your smart contracts. For learning how smart contracts are written, I highly recommend:

  1. LearnWeb3 DAO
  2. CryptoZombies

These resources are mostly focused on Ethereum/Solidity. If you're looking to build on alternative blockchains (like Koinos), the best option is to join their community chat and start talking about what you want to build. Join the Koinos discord server (and say hello 👋)

One last thing: don't put everything on blockchain. You might be tempted to treat it as your database, image host, personal file store, etc., but don't. The easiest way to think about the blockchain's role is that it's for metadata and peer-to-peer computing. The bulk of your data and computation (at least a lot of the time) should most likely move off-chain. Store hashes of your data on-chain, and run code in your front-end when appropriate.

You can always email me if you need any help.


P.S. In case you missed any previous lessons or just want to go back for review, here's your links to all of Blockchain Accessibility Basics: