How to design better experiences for Web3 | by Derick David | Dec, 2021


Web1 was read. Web2 was read and written. Web3 is read, write, and own.

But did people really care back then if the “Web1” could only “read” or “write”?

But technology alone can’t change the world. We’ve seen it many times throughout the past decades with the era of computers, smartphones, tablets, smartwatches, and many more.

As Steve Jobs once said,

“We don’t create technology then come up with ideas for its uses, instead we find problems and try our best to solve it with technology.”

If Web3 isn’t really solving life-changing problems, maybe it’s not really worth the hype. The thing is people don’t care about technology unless you market it as a solution to a real-world urgent problem.

Using it solely for its bravado or appeal is always going to fade out.

And this is one of the biggest issues in the Web3 space is that too many devs launching products for other developers.

Don’t reinvent the wheel

To create design a better Web3, people shouldn’t be able to tell the difference between Web3 and Web2, meaning it should be familiar to current products that we use every day.

For more about digital accessibility, take a look at this article, “Don’t Reinvent the Wheel”, published by the University of Colorado.

It’s possible to have Web3 without feeling its presence.
It doesn’t have to be written all over the Internet.

Quoting one of my friends from Twitter when asked about his thoughts on Web3 user experience.

Twitter user @jonah_sc

Yes, Web3 should be invisible.

Instead of thinking in Web3, think about the problems. Then, focus on one problem, find ways to solve it through Web3.

Source link

Leave a reply

Please enter your comment!
Please enter your name here