The One Question bounty closes Thursday 10 December.

Join in
We Them Media logo We Them Media Support us

The Role of User Experience in Web3 Adoption - Favour Ohanekwu

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

A software engineer at a Web3 authentication company argues that poor user experience is a main reason Web3 has not reached ordinary people. They cite confusing landing pages, gas fees and jargon, and call for simpler onboarding, social login and familiar Web2 design. In questions, they say designers should make the business case to their teams.

Not by We Them Media Channel: Web3Bridge. Published Wednesday 2 October 2024.

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:05 A: Um, please, ladies and gentlemen, join me as I make welcome Favour Ohaneke, as he's going to be talking on the role of user experience in Web3 adoption. Please give him applause as he comes on stage. Thank you. Hi,

0:22 B: everyone. Hi everyone, good morning. Yes, my name is Sylvain. My, my surname is a bit of a handful, so yeah. So today I'll be speaking on the role of user experience in Web3 adoption. So imagine a world where you own total control of your data, right? And you have your trust in not just large organizations like Google and Apple, but you have trust in the technology itself. I believe that this is the promise of Web3. And as promising as this is, have you ever asked yourself, why exactly has everyone not jumped on this? So I will be speaking from an outsider's point of view, a newbie's perspective to Web3. Why exactly are people not jumping on Web3? What exactly is the role of user experience in the widespread adoption of Web3. All right, so as I said earlier on, my name is, um, Fibo Wanoku. I'm a software engineer at Super Tokens. Super Tokens is an open-source user authentication platform. You can reach me via my social media handles. All right, everybody knows of this. The internet started with Web1. Right? And we know Web 1 was more like a read-only, a read-only interface. It was more presentational in nature. So what, what used to happen then was, you know, people just used to view data. They could not really interact. And then Web 2, Web 2 came into, into, into the picture. So for Web 2, what happened was we saw a boost, a huge boost in user experience, right? So internet transcended from just read-only to read, interact, and write, right? So, um, if you think about it, you would see that the adoption of Web2 was more like a no-brainer. And why was this a no-brainer? Because there was a boost in user experience. So I mean, people saw that, oh, instead of just reading plain text, I could interact. Um, user experience in general was much better, so adoption was very easy. So for, for newbies, it was very easy to, you know, just see a Web2 platform and easily interact with it. It was adoption- the entry, the barrier to entry was extremely low, right? And then, um, we believe, I believe, I believe, and everybody also believes that Web3 is the future of the internet, right? And, um, the question we are about to answer here is, we know how much, um, users were really enthusiastic about Web2, how they were very much- it was very much easy for them to adopt Web2. Now the question is, do we have that same level of adoption in Web3? In my opinion, not yet. And why? I believe that there are several factors that drive adoption, right? And for this particular use case, I believe that, I believe, I believe that user experience is one of those factors that is hindering Web3 adoption. So before you fix a problem, the first step is actually identifying or accepting that that problem exists. So the question is, I will ask every- um, somebody in the audience now, do you think that there's a problem? Um, do you think that user experience is a problem right now in this space? Does, does anyone want to answer? Yeah, let's just very briefly- do you really think that user experience has hampered adoption?

4:36 C: Yeah, I do think so. I do think so very much. And, uh, in fact, I will give an example because I was having a discussion with a colleague this morning at the premises, and they were talking about the fact that, say for example, if airdrops were not a thing, if crypto were not a thing, If people are not financially motivated to hunt for crypto, to hunt for airdrops, why people bother about it? And of course, it's not the only application of Web3 or blockchain technology. It's just one out of many, and it's the most widely known one. Because of why? Because it's, it's pecuniarily rewarding. That's why. If there's anything else, if you're not a developer, if you're not a content marketer, if you're not like a professional in the space, a layman, what will I bother about it? So I feel like for us to drive inclusion, for us to drive adaptability, there has to be a lot of evolution and of course better UX. Thank you very much.

5:33 B: Yeah, thank you very much. That's a great answer. So the truth remains that, you know, ask yourself- okay, let me use myself as an example. The first time I, you know, I was on Twitter and I saw Web3, I, I love learning a lot, so I just went on Google Web3 And I tell you, the speed at which I checked Web3 was the same speed at which I left, right? Because you check the first website, you see a lot of graphs, you know, what exactly is happening? You're seeing gas fee. What is gas fee? What is- you know, so I believe that, um, this is a problem. But let's see what people are saying, right? So this is a tweet, a tweet from, um, last year. Someone said, how easy it is for my non-technical parents to book a cab on Uber, but for any crypto wallet app, my parents would hardly be able to register themselves on it. Mastery- Web3 mass adoption has been hindered by complex user experience and onboarding. And this is the truth, right? You can, you can literally tell that a website is web- is in the Web3 space just by looking at the landing page. Yes or no? Sometimes you just see, you see graphs moving animation, you're confused. Right? So it's, it's as though people are building for a particular niche, and that should not be the answer. That should not be the solution for widespread adoption. So this is one of our brothers, our Nigerian brothers. He says we need to port design patterns for Web2 into Web3 to start with for better UX. Most people designing Web3 make it complex already from the start, landing page. And that's true, that's all we've been saying. We need, as developers in this space, we need to start building with, you know, people in mind. And when I mean people, I don't mean people who are already conversant with the field. I mean even newbies, people that have never heard of, of, of, of the space, of the Web3 space. We need to start thinking about them. We need to start building with them in mind. So some of the current challenges that we see in Web3 space today is that number one is there's a very steep learning curve. I believe that in order to function well within this space, there's a lot to learn. How many of you believe it? There's a lot to learn, right? There's also technical- there's a lot to learn, right, on gas fees, staking, smart contracts, you know, for a new mind Right? It might be so difficult for people to understand the complex interface. So I believe that there are 2 forms of cognitive loads, right? There's the intrinsic cognitive load, right, which is embedded in the technology itself. The truth remains that, for example, if you are taking mathematics in school and you decide to take further mathematics, you already know that you will do more mentally. Yes or no? Yes. So there are some cognitive loads that are part of the system, which is acceptable. But there are some cognitive loads that we can manage ourselves, right? Things like complex interfaces. We shouldn't do this. We shouldn't, you know, use jargon terms, right? Let's simplify wordings for easy adoption. So some of the techniques that we can use to improve UX are things like simplifying onboarding, enhancing design consistency. This is very, very important- design consistency. I believe that we should be able to port design patterns that people are already familiarized with in Web2, right, to Web3, so that people don't need to learn more. People don't need to learn too much in order to understand the space. Are you with me? How many of you believe- how many of you agree what I'm saying? Good. So for example, simplifying onboarding, you know, guided tutorials, social logins. As I said, we need to start porting things that people already know in Web2 to Web3 in order to improve adoption. Um, so lastly, as some- the truth is, as some platforms getting this right, there are a few. If you look at Web3 platform in 2022 and 2024, they are different. Yes or no? Actually, people have started building with naive people in mind, and I, I believe that that is a step in the right direction for us, right? Because of our time, I have to rush this. So key takeaways: we have simplifying onboarding is very critical and very, very, very, very critical. Consistency, continuous improvements, balancing security. I know we want security, but we Usability has to also be in mind while we do this. All right, thank you very much. That's my time. Please, a

10:25 C: round of applause. A round of applause. But before you leave, questions. Okay, please take questions.

10:31 B: Does anybody have any question?

10:36 C: Yeah, question.

10:36 D: All right, hi, thanks so much. That was a really great talk. Um, my name is Peace and I have 2 questions. So the first one, like you said, um, and I fully agree with you, the user experience is really convoluted right now. It's very hard for new people to get into Web3. So how do we- okay, yeah, how do we encourage more designers to like adopt the practice of creating, let's say, easier workflows that people can use to onboard?

11:09 B: Yes, for sure. Um, so one step is, you know, speaking about it. I think people need to speak more about it. I think the reason why people right now do not speak about it is because it's mostly people who understand the domain that use it, so they don't talk, right? But, um, what needs to happen is we need more people to talk about this. Companies need to also enforce this, right? Web3 companies need to enforce this. When you are designing, you need to ensure that you design some naive people, people that don't understand the space too. Yeah.

11:44 D: All right, thanks. And for my second question, there are for sure a lot of UX and even product designers that definitely tilt in towards more simple, I say, programs and apps that people can use. But in cases where they work with teams that do not prioritize this, how do you encourage, or how can they, like, will I say, phrase or be able to talk to their teams about it and encourage them to use versus simpler processes.

12:10 B: Correct. So one thing, I think this happens everywhere. If you've worked for very large enterprises, you would notice that sometimes there are a few dogmas. They have pretty defined ways they do things, right? But in order to effect changes, you need to, you know, speak to them. If you're, for example, I'm a UX designer, you need to speak to them as regards the advantages that designing in simpler ways will bring to the companies. Right? In order to change the direction of a team, you have to actually, you know, put up a very good case for why they should follow your pattern. Do you get what I mean? So I believe that on the part of the designer, you need to be able to convince enterprises, convince your team as to why they should do this. If they don't see benefits for doing it, they would not adopt it. Do you get

13:02 D: what

13:03 B: I mean? Thank you. Thank you very much. Please, a round of applause.

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.