The One Question bounty closes Thursday 10 December.

Join in
We Them Media logo We Them Media Support us

Designing for Web3: Crafting Useful Products, Beyond DAOs, DeFis, and Wallets - Mercy Kolapo

The picture loads from YouTube. The player loads only when you press Play. Turn on captions in the player if you need them.

A product designer who gives the name Tumininu speaks at Web3 Lagos on designing useful Web3 products for everyday people. They say designers should hide blockchain complexity with plain language, social login, clear warnings on irreversible actions and mobile-first design. They advise learning the basics, joining communities and working with developers.

Not by We Them Media Channel: Web3Bridge. Published Tuesday 9 September 2025.

Titles are the owner’s. It plays from their channel.

Transcript

This transcript may contain errors. This video belongs to Web3Bridge. Letters mark each change of speaker.

These are the speakers’ own words. We have not checked their claims.

0:01 A: So the next speaker is going to be talking to us on designing for Web3, crafting useful products beyond DAOs, DeFi, and wallets, in person of Mercy Luatsuminu Kolapo. A round of applause for her, please. Thank you so much.

0:18 B: Do we have designers in the house? UI/UX, graphics? Brand identity. Fashion designer. Okay, so my name is Tumininu, and I'll be speaking briefly about crafting useful products beyond DAOs, DeFi, and wallets. So I have a friend who is a designer like me. I'm a product designer, by the way. So some years ago, we were having a conversation, and he was- he has vowed with his life not to have anything doing with Web3. So we were- I was, I was asking him why, because it was a conversation, and he said he does not understand anything. Like, you know, designers are supposed to be problem solvers. Our job is to translate complex problems into beautiful experiences for people. But now the designer does not understand what Web3 is. It was- I think it was around that time when there was this NFT marketplace thing. So it was so complicated for him, and I was not equipped enough to convince him or to continue the conversation. So it was just there. And this is a bigger problem when designers who are supposed to be solution providers, they do not understand the problem. They cannot provide or translate the problem into a beautiful experience for users. Thank you. So yeah, there's a complex UX problem of Web3, like the onboarding process, trying to onboard users or trying to, trying to design a flow that brings people, that onboard people to, that makes people use a product or a solution we are trying to provide. And also reconciling the transparency of blockchain with the Privacy expectations. It is sometimes it can be so difficult to communicate this to people like who are new to Web3. And this is our job as designers. It is our job as designers to make this communication as seamless as possible. And a way to do this is to- What to do this is to design for everyday users, like a way to approach solving this problem is to design or build solutions for everyday users. What people want to use every day beyond, um, beyond DeFi, beyond wallets. Because DeFi are cool, but what we have right now, they are like, um, built for crypto nerds or people who are already familiar with Web3. But if you want to drive adoption and want people to, to really understand what Web3 is, we need to consider designing for everyday users. We can bring in already existing solutions from Web2 and design it through a lens of Web3. So yeah, we need to- in order to drive adoption, we need to consider building products, more practical tools for everyday users. Is this working? Okay, so who is a Web3 designer? A Web3 designer is simply a designer who designs for Web3. It is as simple as that. We are bringing our skill sets from wherever we are coming from, Web2. We are bringing that knowledge and we are, um, using it to build useful products on Web3. So a Web3 designer helps translate complex blockchain tools into simple helpful and even delightful experiences. Sometimes, depending on your career trajectory, you may want to consider learning how to write code, but it is not very important. We just need to understand the basics in order to provide the solution, in order to build useful products for people. So our job is to craft human-centric, human-first experiences for the blockchain while making it easy. For everyday use. So that's our job as Web3 designers. Okay, so there are core principles of UX in Web3. These principles are- they are not new. It is not when Web3 appeared that they now invented a new UX or some core principles for Web3. These principles are what we are familiar with, like right from time, the normal laws, the normal UX laws, just that this time we are applying these laws, these, these principles that we already know, we are applying it in building products, useful products for Web3. So the first thing is, um, to introduce the blockchain gradually. We are- if we are designing for everyday users or we are building products and solutions for everyday users, we must assume that they don't know anything. We must assume that people who are going to use these products are ignorant and they don't know anything. So we should introduce the blockchain or we should introduce Web3 gradually to them. And the use of friendly language. We should, instead of saying verify your identity with a cryptographic signature, say click to confirm you are the owner of this profile. Like, this is just the basics. You need to communicate as clearly as possible. Thank you. And we should use friendly language, a friendly language, like while trying to communicate whatever we are trying to. So the next one is feedback loops and clarity. Always let users know what's happening with tailored copies. You can use microinteractions, microanimations, just make them know what is happening. Then the next one is account abstraction and social login. I don't know if you've tried to use a Web3 product and you are thinking that you have no business connecting your wallet. Like, you're just thinking within you that you- why am I connecting my wallet? I just want to upload something quickly and they are asking me to connect my wallet. And some, some products will even say, okay, you can only connect your Argent wallet or your, um, which other wallets. And it- which is okay, by the way, because of how the product is being built. But sometimes this can This can slow down onboarding. People may find it difficult if they are, they are trying to install an extension or install a wallet in order to use your product. So what we can do is to use what people are familiar with. There's something called Web3 authentication. In fact, if connecting wallets is that important, they can do it later. Like you can Allow them experience what you've built for them. Allow them experience the solution before telling them to connect wallets or just use Google login, social login that people are familiar with because we are trying to introduce Web3 to them gradually. So we should we should be open to consider these other options in order for us to to also drive adoption and onboard people easily. So it is also one of the core principles of UX, like applying. the already existing UX principles in Web3. So the next one is anchor trust. There are a lot of irreversible actions on the blockchain especially, and we must be able to communicate this as clearly as possible, that this thing you're about to do, there's no going back. Once you've done it, that's the end. We should not be using dark UX or something that will make people run away from, from the solution we built for them. So we should make sure to confirm irreversible actions, explain fees in plain terms. And the next one is mobile-first design. We should consider the fact that Africa is a mobile-first ecosystem, and a lot of people are going to access whatever solution you are providing for them through their mobile phones. So whatever solution we are designing or providing, it should be mobile responsive. So I already mentioned the Africa-first advantage, like we can bring in already existing solutions, what people are already familiar with from Web2, we bring it to Web3 and design it like through the lens of Web3, use and put something that will make people want to actually make use of. the solution we are providing. So, 2 years ago during Config- Config is Figma's annual conference. So Brian Chesky said something. He said you can- and I quote- he said you can design the world you want to live in. You don't need permission. Speak up. Push your vision. If you are leading design, try to shape how the entire company thinks. Thank you. Designers can run companies. They can build. They can ship. And during config this year, someone also mentioned it. I don't know who exactly, but I could see from people's stories that someone was encouraging designers to be founders. That since we understand problems and our job basically is to translate problems into beautiful experiences, why don't we just take ownership? Like we can ship products, right? So we can build products from scratch to launch. And this is me encouraging anyone who has any idea as a designer, like you can, you can be a founder, you can, you can build products like real solutions for people. So if you are transitioning into Web3 as a designer or you are just getting started, you might not even be a designer. Yeah, I wish I had a background knowledge of how to get started when, when I started. I think I started designing for Web3 4 years ago, and it's, it's, it has just been okay, learning from here, learning from here, learning from here. It was, it was not easy. And here are some things that I learned, I have learned over the years. The first one is to learn foundational concepts, and you can learn this from, um, learnweb3.io. There are free courses online where you can really learn the basic, basic, basic, basic thing. Like, you need to know what some of these terms are. You need to know the difference between gas and gas fee. If you are designing for DeFi, you need to know what smart contracts are. You need the background knowledge if you want to provide a solution. Like for people using Web3 as a technology. So you need the basic knowledge. You need to have the basic knowledge. You need to learn the foundational concept of Web3. Then the second one is redesign the flow you use every day through a Web3 lens. It might not even be a flow you use every day. It might be something, maybe just an idea that you have in your head and just redesign it through. This is, this is you practicing, right? So then the next one is join Web3 communities. This one is very, very, very important. Very important. There will be someone in a community who has walked the path you are about to, who will be willing to hold your hands through and guide you through. There will be someone within a community who will be willing to collaborate with you and explain things to you, things you will not just find and learn on your own. So it is very important for you to belong to Web3 communities, whether they are design-friendly or whether they are um, your career friendly or not. You need to join Web3 communities, active ones actually. Then collaborate with Web3 developers for hackathons and world-class projects. Some people also, they, they may lack, um, you may lack ideas or you may not know what, what may actually fly. And a way to gain hands-on experience is by collaborating with developers. And most times you will find developers in communities if you just go to your, maybe your WhatsApp status, to announce that, oh, you are looking looking for a developer to collaborate with, this is- they will not answer you because everybody is looking for money. But if you belong to a community and maybe you have an idea and you need someone, or you need developers, or you need other people- because you are not the only one in a community, there are other people within the community who will have interest in whatever idea you have. So it is, again, it is very important to join Web3 communities, active Web3 communities, because that is where you will find people who are of the same mind as you. So then use chain abstractions, social login tools, and progressive onboarding to simplify complexity. So make sure that as you are trying to provide the solution or whatever, whatever idea you are trying to implement, you are also keeping it in mind that we have an onboarding problem in Web3, and you are Solving this problem as much as possible. Yeah, last month I took a course. It's a developer course actually. It is not very design friendly, but because of my background, I used to write code before I transitioned to design. It was quite easy for me. Like it was, it was, it wasn't something so difficult for me. And I, I got reminded of how as much as designers are trying to understand users, understand their pain points, and provide solutions to those problems, we also need to consider the already existing solutions. We need to consider the workflows from developers. There are some things that we will not be able to change as designers. And if we come up with solutions, when we come up with solutions, we feel like This is the right thing. This is the absolute thing. It may not be compatible with the solution that the developers are providing. So taking this course made me know something that as much as I'm- it reminded me of something that as much as I am designing for people and providing solutions for people, I must also consider I'm seeing the solution from the end of the developer as well, like what is already available, and I'm working hand in hand to translate To translate the solution and the problem or the pain points to in order to come up with something that will work, something that will not give people problem. It will not give the users problem. It will not give the developers or the other people working on the solution problem. So yeah, I'm learning how to translate all of these things. I learned or I'm still learning how to translate all of these things into trust through copy flow and clarity. So the summary of all I've been saying since is, um, the fact that Web3 adoption fails not for the lack of tech, but for the lack of human-centered designs. And we as designers are here to bridge that gap, to solve that problem. So designers are very important. Our job is to translate the tech, the solution, into trust and make people actually embrace the solution. So, We should make sure to use the power of progressive disclosure, account abstraction, and human-friendly human language to communicate this solution to users. And, um, we already have the ecosystem. Africa's real-world patterns are the world's next Web3 opportunity. So we should start now and design something that works and something that does use- actually, it has to be beautiful and it has to work. So thank you for listening.

17:01 A: Thank you very much. A round of applause for her, please. Thank you.

More from this hub

Something wrong, or a video you want off this page? Write to wethem.xyz@gmail.com and it is fixed or taken down within 48 hours.