Web2 to Web3: What Changes When You Add Blockchain

If you've built software before, you have intuitions about databases, APIs, deployment, and product iteration. Most of those intuitions still apply — but a few fundamental things change. This guide maps those changes for experienced Web2 builders.

The Database Is Now Public and Immutable

On-chain state is like a database everyone can read and no one can delete. There's no DROP TABLE, no soft delete, no GDPR erasure. Data written to a smart contract is permanent. This changes what you store on-chain (only what must be trustless and permanent) vs in a traditional database (everything else). It also has legal implications in certain jurisdictions.

You Can't Fix Bugs in Production

In Web2, you push a fix and users get it in seconds. In Web3, a deployed smart contract is immutable. Bugs are permanent unless you built an upgradeable proxy (which has its own security tradeoffs). This means: security reviews before launch are non-negotiable, and iteration speed on-chain is fundamentally slower than Web2. Accept this and plan your MVP scope accordingly.

Users Own Their Data (Sort Of)

On-chain assets and state are cryptographically owned by the user's private key — no one can confiscate them without the key. This is genuinely new. The practical implication: you can't reset a user's password, you can't reverse a transaction they regret, and you can't freeze their account (unless you built those capabilities into the contract). Users have more sovereignty and less recourse.

The UX Layer Is Separated

Your frontend is an interface to a decentralized backend. The 'backend' (smart contracts) exists independently. Anyone can build their own frontend to your contracts. This is good for decentralization; it means you need to think carefully about what's enforced in the contract vs what's enforced in the UI. UI-only enforcement can be bypassed by anyone interacting with the contracts directly.

Gas = Operating Cost Paid By Users

Every on-chain operation costs gas. Users pay this, not you. Complex operations (nested loops, large arrays) cost more. This changes how you think about logic placement and data structures — you're optimizing for user transaction cost, not server compute cost. L2s dramatically reduce this burden, but it never goes to zero.

Latency Is Different

On Ethereum mainnet, transactions take 12 seconds to confirm. L2s are faster (1–2 seconds). Solana is sub-second. But there's no HTTP 200 in 50ms for on-chain operations. UI design must account for transaction confirmation time — spinners, status tracking, and optimistic UI updates are essential. The Web2 concept of 'request → response' maps to 'transaction submission → mempool → confirmation.'

The Business Model Changes

Web2 business models (subscription, ads, data monetization) don't map cleanly to Web3. Common Web3 models: protocol fees (% of transaction volume flows to treasury/token holders), NFT sales (primary and secondary royalties), token appreciation (protocol value accrues to token), and service fees (charge for premium access to the dApp UI). Each has different regulatory and sustainability implications.