Will Little Subscribe

The paradigm shift: Decentralized Application (dApp) development in Web 3.0

Click here to view this email in your web browser

Greetings all,

In this week’s episode of Ventures, I start with a quick summer 2021 reflection and then dive into a short clip from Episode 48 with Andrew Cronk. Web 3.0 entrepreneurs and decentralization application (dApp) developers will need to approach software engineering concerns such as user identity and data storage/querying in different ways than the Web 2.0 era. Andrew’s initial insights into this transition are enormously helpful.

Check it out: Web 2.0 vs. Web 3.0 development, design, and data architecture concerns :: with Andrew Cronk

A new paradigm

As a web/mobile developer over the past couple of decades, I have gotten used to thinking about user identity, data storage, Standard Query Language (SQL), relational database, key-value stores, web development frameworks like Ruby on Rails, DevOps environments like Amazon Web Services, etc… as centralized applications with code and data stored on servers (or services) that I can directly control.

The problem, of course, is that this Web 2.0 paradigm has led to the hot mess we’re in with data privacy issues and hackable silos.

There are better exerprices coming around the corner quickly. We will own all our own data, have it secured on blockchains, permission it out to brands/orgs/governments we trust, and participate in decentralized apps (dApps) that we want to engage with for social media, eCommerce, games, etc…

This is a future I’ve been writing and thinking about a lot this past year, and it’s a future I am highly interested in helping to build and fund.

If you are a Web 3.0 product manager, entrepreneur, and/or software developer, I’d love to hear from you. Let’s start a conversation about how we can combine our networks and build a better Internet together.

Have a great rest of your week!