Who this Guide is For
This guide is for those looking to build an application, game, or other tool that utilizes a blockchain backend while providing a seamless, Web2-like user experience. By embedding a wallet into your application, you can serve as your customers’ gateway to Web3 without compromising your brand or user experience. In this guide, you will learn about embedded wallets and key considerations for integrating them into your application.
Intro to Embedded Wallets
Wallets are essential tools for securely storing digital assets, authenticating users, and authorizing transactions on the blockchain. They come in various forms, with the most commonly used being third-party browser extensions like Phantom or MetaMask. While powerful, these wallets can disrupt the user experience in decentralized applications due to pop-up approvals, inconsistent branding, and the need for users to manage separate tools/log-ins.
Since wallets are the primary interface for users to access and interact with decentralized applications (dApps), utilizing an embedded wallet can streamline the user experience. Embedded wallets are integrated directly into your application, allowing you to manage the look, feel, and experience of signing and approving transactions and reading blockchain data. This integration provides a cohesive user experience, aligning the wallet interface with your application's branding and design.
Why Embed a Wallet in Your Application?
Embedding a wallet into your application can offer significant strategic and operational benefits, enhancing both user experience and business opportunities:
Streamlined user onboarding and engagement: keep your users in your app without introducing 3rd party extensions, click-throughs, sign-ups etc.
Brand Loyalty: A seamless and engaging user interface for interacting with your ecosystem can strengthen customer relationships and create a product that users love. By embedding a wallet, you maintain consistent branding and UX, which fosters trust and loyalty.