๐งฉ dApp Decentralized Application
An app whose core logic runs on a blockchain through smart contracts instead of one company's private servers, so no single owner can quietly control, change, or shut it down. You use it through an ordinary website, but you act by signing transactions with your own wallet.
๐งฉ The simple version โ a vending machine, not a kitchen
A normal app is like a restaurant kitchen you can't see: you place an order, and the company decides what happens behind the counter, in its own private database. A dApp is more like a vending machine bolted to a public square. The rules are printed on the front for anyone to read, anyone can walk up and use it, and no staff can secretly change your order. That public, can't-be-quietly-edited machine is a smart contract โ code living on a blockchain that runs exactly as written.
๐๏ธ A dApp is two halves
Almost every dApp is built from two parts, and only one of them is on the blockchain.
| Part | What it is |
|---|---|
| โ๏ธ Backend (on-chain) | Smart contracts that hold the rules and the records. Once deployed, the code can't be quietly changed and it keeps running with no single owner in charge. |
| ๐ฅ๏ธ Frontend (off-chain) | A familiar website or app โ buttons, charts, menus. This is just the friendly face; it often runs on ordinary servers like any other site. |
๐ This split is why a dApp isn't automatically unstoppable. The contract can live on even if the website disappears, but the website can also go down on its own.
๐ How it feels different to use
In a normal app you click a button and the company performs the action for you in its database. In a dApp, you perform the action: you trigger it by signing an on-chain transaction, usually through a wallet. Nobody does it on your behalf, which is why the wallet pop-up asking you to confirm shows up so often.
๐๏ธ What dApps are used for
- ๐ฐ DeFi โ lending, borrowing, and earning without a bank
- ๐ DEXs โ swapping one token for another with no middleman
- ๐ผ๏ธ NFT marketplaces โ buying and selling digital collectibles
- ๐ฎ Gaming โ games where items live in your wallet, not the studio's database
- ๐ณ๏ธ DAOs & governance โ communities voting on shared rules and funds
โ๏ธ The upsides and the catches
| ๐ Why people like dApps | ๐ Where they get clunky |
|---|---|
| No central owner; hard to censor or shut down | Hard to update or fix after deployment |
| Open-source code anyone can audit | Limited throughput โ can get slow and expensive when busy |
| Tamper-resistant records and real user ownership | Awkward UX: wallets, gas fees, and seed phrases scare off beginners |
๐ Real examples you may already know
Uniswap (UNI) is one of the best-known dApps: at heart it's a set of smart contracts plus a web frontend that lets people swap tokens on Ethereum without a company in the middle. Aave (AAVE) is a DeFi dApp for lending and borrowing. For most beginners, the first dApp they touch is exactly this: connecting a wallet to a token-swap site or an NFT marketplace.
โ FAQ
- Is a dApp just an app that lives entirely on the blockchain?
- No. Only the backend logic, the smart contracts, runs on-chain. The part you see and click is an ordinary website or app, often hosted on normal servers just like any other site.
- Does using a dApp mean no company can ever control or stop it?
- Not fully. The smart-contract backend is hard to change or censor once deployed, but the frontend website can still go down or be taken offline, and some dApps keep centralized pieces like admin keys. The contract can outlive the website, though.
- How do I actually use a dApp as a beginner?
- You usually connect a crypto wallet to the dApp's website, then approve actions by signing transactions in that wallet. Most people first meet a dApp by connecting a wallet to a token-swap site or an NFT marketplace.