Lesson 04: Why Build Decentralized?
Embark on your journey to building production grade apps.
Remember Lesson 3? You learned everything that goes into making an app production-ready. A database. Auth. File storage. Payments. Email. Error tracking.
Every item on that list is a separate service you don't own. Every one can break, get hacked, freeze your account, or disappear overnight.
Underneath all of it is one fact: you have to trust someone.
You trust Supabase to keep your database online. You trust Stripe not to freeze your funds. You trust AWS not to go down. You trust the platform not to change its terms and lock you out tomorrow morning.
This isn't hypothetical. Social platforms have banned users overnight after a single policy call. Payment processors have cut off merchants under public pressure. Apps that millions of people relied on have been pulled from app stores. The pattern is always the same: someone built on infrastructure they didn't own, and someone else decided to pull the plug.
A different way to build
What if trust wasn't a dependency?
That's what decentralized apps are for. There's no company in the middle that can decide, one Tuesday, that you're off the platform. There's no server a government can seize. The app runs on a network of computers that no one owns and no one can shut down.
You've used decentralized tech before. BitTorrent works this way. No company runs it, no one can turn it off. But BitTorrent only shares files. For apps that handle money, run logic, or store real state, you need the specific kind of decentralized network this course is about.
What's the core difference between a traditional app and a decentralized app?
Why it matters
Most of what's been built on blockchains so far is, to be blunt, casino stuff. Scam tokens, pump-and-dumps, rigged games. A lot of people used this technology to extract money from each other.
That says something about the people, not the technology. When the technology gets used well, it does things nothing else can.
When banks froze transactions to Gaza and cut off millions of people from aid, crypto wallets didn't. Donors sent money directly and it arrived, because no bank was in a position to block it.
When governments pressured domain registrars to seize websites, ENS gave people domain names nobody could take away.
When centralized exchanges froze user accounts and blocked withdrawals, Uniswap let anyone swap tokens without asking permission.
This is all happening right now.
What hasn't been built yet
Here's the part worth sitting with: the mainstream decentralized app that people use for something other than speculation or finance doesn't exist yet.
Billions of dollars have been raised. Hundreds of teams are trying. Most are still building casinos.
Meanwhile, the real problems are sitting there waiting:
- Anti-censorship tools
- Verifiable identity and voting
- Data privacy that users actually own
- AI-content detection that can't be faked
- Governance systems that can't be captured
- Ownership that no platform can revoke
Every one of these is a billion-dollar problem. None of them have been solved well. The reason isn't that the technology can't do it. The reason is that most of the people building the technology aren't thinking about users.
Why you
You know how to think about users. You know what makes an app actually good. You're now learning the technology that lets you build things no platform can take away.
That combination is rare here. Most people in this space have one side or the other.
The decentralized app people actually use hasn't been built yet. It might be yours.
Next up
You understand why to build decentralized. Next lesson: the specific network we'll build on.
0/1 correct
0% — get all correct to complete