Discussion on Dapps/Web3 and Web2 with blockchain based on use cases

One of the reasons I believe that apps that use blockchain do not get much popularity with the general public is that devs usually put the tech and blockchain ahead of the real customer needs, going all in on chain difficulties, creating a big entry barrier all because it is cool, decentralized, or censorship resistant,but most of the time these things do not matter for their product or customer.

Supposing I want to build a podcast app that is 100% legal and compliant with the law, with a value proposition to share a fair profit with creators. Why not build mainly using traditional Web2 on the cloud and use the chain only to solve the problems that crypto and the chain are good at, like transactions, commissions, Daos, etc.?

Don’t get me wrong here, but I see a lot of criticism from the blockchain community (in general) defending everything on the chain. But why not mix? This mixed approach would leverage a much better user experience in the applications and, with time, educate people about the chain.

15 Likes

I think There’s nothing wrong with mixing Web2 and Web3. Foe example a podcast app, where content and community come first and If we want mainstream adoption, the user experience has to come first .

4 Likes

The point is solid, but sometimes the obsession with putting everything on-chain complicates innovation and user experience unnecessarily. Hybrid solutions make a lot more sense, yet the community still struggles to find that balance.

1 Like

Totally agree. Web3 shouldn’t be everywhere — just where it adds real value. Mixing Web2 for UX and Web3 for ownership or incentives is often the smarter path.

4 Likes