Web3 DAPP user experience best practices

This article will introduce Web3 Decentralized applications （DApp） User experience （UX） Some best practices to follow .

Learn in a familiar language The etheric fang Web3 DApp Development ：Java | Php | Python | .Net / C# | Golang | Node.JS | Flutter / Dart

With web3 Application's Growing popularity , A large number of new users are pouring into this field . Most of them are trying to decentralize applications for the first time , Entry barriers for non-technical users remain high .

New users need to learn more than just wallets 、 The key 、gas Fees and other terms , and dApp It doesn't make it any easier .

This space is growing so fast around a community of mostly developers , So that we forget the standard and good user experience practice . This is very similar to the early days of the Internet , Developer 、 Geeks and early adopters dominate the scene , Because the underlying technology is a little rough , Usability has also been left behind .

In countless applications , Some are well made and stand out from the public , But most still lack basic usability , As a trade-off to enter the market competition as soon as possible .

I'll cover some of the best practices that every decentralized application should try to follow , To improve their user experience through good and bad examples .

please remember , These are just some （ Usability issues ）, Not an exhaustive guide to all questions . If you want to read more about Blockchain design principles Information about , I would recommend Sarah Mills The article , These articles are still very important today .

For more beginner resources , Please check this aggregate .

1、 What is? dApp？

dApp Or decentralized applications are taking advantage of web3 The decentralized nature of software applications .dApp The core idea behind this is that users have their own data , Not with dApp Shared by the creator or any third party . This is through the wallet 、 Login and authentication 、 Distributed database and file storage system （ Such as IPFS ） It's a combination of .

2、Web3 UX Best practices - Do not automatically connect your wallet

Sometimes when visiting a new dApp when , The first thing that happened was Metamask Opening requires you to connect your wallet .

This is actually an annoying practice , It is also a bad practice .

Users have no chance to check your website or the content you provide , They were asked to promise to connect their wallets . It's not that bad things will happen , Instead, hijacking users from their primary experience into new windows or pop-up windows is something we need to avoid .

Connect the wallet to the web2 Registering or logging in to your account in the scenario is very similar .

You need the user to make a choice , Instead of imposing on them .

3、Web3 UX Best practices - Create meaningful interfaces in fewer terms .

Web3 The application comes with many new terms that may initially confuse the user . therefore , It is important to use as simple a language as possible .

When something cannot be explained in simple terms , There are exceptions. , under these circumstances , It is always useful to add tooltips or links to documents or resources .

4、Web3 UX Best practices - Create user guides and operation Guides .

many DeFi Each agreement has its own wiki And user guide , But they are not always easy to find or poorly maintained , Because they are not the main focus of the product .
On the other hand , If you're a developer , Then the resources will be more abundant .

A good compromise for large documents is in UI Add a helper program to the , In this way, users will never leave the main experience .

5、Web3 UX Best practices - Don't keep users away from the main experience

As mentioned in some of the above points , It is not a good idea to bring users out of the main experience , And shifting attention to other things can break the user process .

If you are trying to create a transformation and let users try your dApp , Then the linear process from start to end is easier .

6、Web3 UX Best practices - Don't hide important information , Do not mislead users .

Transaction fees or treaty taxes are not always advertised , Users will feel betrayed when they find out .

It should be very clear how much your agreement will charge for the interaction , Include （ If possible ） Expectations on the web gas cost . On some chains ,gas The cost is negligible ,
But if you run on the Ethereum main network , At least let the user know the possible high gas Expense is a good practice .

7、Web3 UX Best practices - Clarify the network being used / Blockchain .

This should be a must , Especially in the growing side chain environment , also L2 The solution does not always know which chains your protocol runs on .

If your application supports multiple links , Let users switch between chains , Or if you only operate on one chain , Let the user know by displaying the name of the chain .

8、Web3 UX Best practices - Always tell the user what happens at each stage of the process .

If in dApp Deal in , Always be sure to show them and their status somewhere .

It's easy for new users to panic about what's happening and whether they've taken the right steps to complete the task .

clarify DApp The contract address with which you are interacting , And whether there are multiple clearly marked them .

After submitting the transaction , Users should be able to view links to transaction details on the block browser .（ Some of them are not really user friendly , But if you're talking to someone on your team for support , This is very helpful for debugging ）.

Last , Review what is about to happen or just happened , For example, trading volume 、gas Cost and expected time .

9、 Conclusion

I hope this simple list of good practices will help you create a more user-friendly dApp.

We have a long way to go , From comprehensively improving technology to making it more seamless and integrated , But we can at least cover up some of these shortcomings by providing better usability .

---

Link to the original text ：Web3 DApp User experience best practices — Huizhi. Com