The One Question bounty closes Thursday 10 December.

Join in
We Them Media logo We Them Media Support us

Building Scalable Web3 Applications - Amani Kanu

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

A frontend engineer and tech advocate talks about building Web3 apps that scale. They explain what Web3 is, why easy design matters for adoption, and how React and Next help. Practical tips include lazy loading, code splitting, state management tools and batching transactions. They urge the audience to ask questions and connect.

Not by We Them Media Channel: Web3Bridge. Published Sunday 13 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:12 A: Okay, so I'm talking on building scalable Web3 application for those doing front end. So first of all, first of all, about me. My name is Amanikano. I'm a tech advocate. Um, I do a lot of things. I'm a community person. I'm a senior frontend engineer. I love to bring people to tech. And also one thing about me is that people call me the tech evangelist. I don't know why. Okay, let's go. So understanding Web3. So for us to really do justice to it as a frontend engineer, first of all, you need to understand what, what is Web3. Web3 is the decentralized web, uh, is a decentralized web powered by blockchain technology. And, uh, is also, um, Web3 focus on ownership, transparency, and control of data by users. Uh, Web3 eliminate the middleman, like what we have, like the government. It, it enhance security and privacy. So, uh, the next one is overview of Web3. One is that Web3 represents the next evolution of internet. The next one is that Web3, uh, focus on user ownership, data privacy, and blockchain-driven application. Uh, the next one is, um, there's a major shift from Web2 to Web3. Sorry, I'm trying to rush so that I'll meet up with my time because I have like 5 minutes left. Okay, um, so importance of, uh, scalable and user-friendly application, um, which is, uh, decentralized application with ADAPs. Uh, one is that, um, the success of Web3 relies on building applications that that are not only decentralized but scalable and easy to use. Uh, 2 is that user, uh, user experience remains a critical factor in mass adoption. So for us to be able to adopt Web3, there's that user, um, user experience that must be, that must be ahead too for people to adopt it. And then the next one is, uh, scalability challenge. Like some of the previous speakers have, have said about this. So the next one is the role of modern front- uh, modern front-end framework. One is that, um, front-end framework like React, Next provide tools to build interactive, very fast, and responsive user application. They help bridge the gap between decentralized technology and end user by delivering familiar smooth user interface. The next one is that enable developers to handle state routing very seamlessly. So if they're coming from the Web2, it's easy for you to move to Web3 with, with with this. So how frontend framework enhance Web3? That's with ADA performance. One, efficient state management. Efficient state management to optimize rendering techniques like applying improved load time and responsive. The next one is the scalable architecture. Support growing user base and complex ADA functionality. So, um, the next one, integrating Web3, uh, into, uh, what we are doing now. Integration of Web3 technology. One, what you need to do, you set up your environment. How do you set up your environment? By installing Node.js, React, and Next. The next thing you need to do is you need to choose the right tool. What, what are the right tools for, for frontend engineer? One, you need to either use Web3.js or Edge.js. These are like tools that you can use to connect directly to write on the block or read from the block. The next one is the state management. You can use any of the state management that you have. So I'm trying to rush. So best practice to build a scalable dApp. One is that you need, you need to optimize the, the performance from your React application. You can lazy load, code split, um, do your rendering, efficient rendering. And also for efficient state management, you can use Context API, Redux, Global State, and every other state management tool. The next one is handling large-scale transaction. For you to handle large-scale transaction, you can do batch processing, um, and also to manage a scalable API and Node. Um, okay, so I'm almost at the end now. I hope I'm, I'm in time. So building a scalable web application means designing for the future, and I want us to do this. The only bad question is the one not asked. Turn to your neighbor and ask a question because you don't know that- you don't know if that your neighbor is the next happening thing. Connect and connect and connect. Ask anybody question. Okay, so thank you. Is any other question for me? Is any question for me? Any question for me? Okay, no question. 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.