# Unified Wallet And Dapp Interaction - Beacon

The user experience of Web3 applications is not on the same level as their Web2 counterparts. The entry hurdle for new users to be onboarded to decentralized applications (dapps) has been cited as one of the major requirements towards acceleration of mass user adoption. Setting up a wallet, wanting to interact with a new application and realizing that the flow to connect to the application is either non-existent or completely different, is immensely frustrating for users. This frustration leads to users drop off, before even interacting with the application.

## Challenge
The user experience for wallet and dapp interaction in the Polkadot ecosystem varies from application to application. Due to the nature of Polkadot’s technology stack with Parachains and agile coretime in the near future, the challenge for Polkadot-related project is somewhat amplified when it comes to support for wallets and their interaction capabilities. 

Parachains have the ability to expose multiple environments to end-users: native Polkadot SDK, EVM, WASM and others. 

In the beginning PolkadotJS saw the creation of a simplified browser extension wallet, that allowed users to quickly onboard to a completely new technology and in extension explore the state of the various chains with the PolkadotJS App and interact with them. PolkadotJS is a powerful developer tool and is perfect for newly bootstrapped Polkadot SDK chains.

Unfortunately, some public perception stuck and even though there are amazing wallets like Talisman , SubWallet , Nova Wallet  and others, a subset of users still view the PolkadotJS Extension and App as the go-to-wallet and criticize the user experience.

## Ambition
Wallet interaction should be familiar for users and provide a user experience that is replicated across all applications in the Polkadot ecosystem.

1. Users can easily connect to an application with their favorite wallets, the same user experience is provided for wallets such as:
Browser extensions, Mobile wallets, Desktop wallets, Web wallets, Hardware wallets
2. The user-facing interface is unified for all environments supported in the Polkadot ecosystem, including: Polkadot SDK chains, Polkadot SDK chains with an EVM environment, Polkadot SDK chains with a WASM environment
3. Application developers have one Typescript SDK that they can easily integrate into their dapps with a few lines of code.
4. Applications developers can configure their integration to their need, change the end-user interface e.g., featured different wallets, utilized dark mode and much more.
5. The SDK is compatible with multiple transport layers, the layers responsible for passing messages between the application and the wallet, supported are: Browser Extension Message Passing, Beacon peer-to-peer (p2p) network, WalletConnect

## Feedback
We would love to get your feedback on this proposal.  
**[Find more details in the full proposal](https://drive.google.com/file/d/1-VJNOfGw2HClzicM5Qsv1yPWGUeQaCMD/view?ts=65c4ca06)**

Unified Wallet And Dapp Interaction

Treasury

Problem Statement:
- The user experience of Web3 applications in the Polkadot ecosystem is not on par with Web2 applications, leading to frustration and drop-off for new users.

Significance:
- Improving the user experience for wallet and dapp interaction is crucial for accelerating mass user adoption of decentralized applications.

Proposed Solution:
- Develop a unified wallet and dapp interaction solution called Beacon that provides a consistent user experience across all applications in the Polkadot ecosystem.
- Users can easily connect to applications with their favorite wallets, and developers can integrate Beacon into their dapps with a few lines of code.
- Beacon is compatible with various wallet types and transport layers.

Expected Outcomes:
- Improved user experience and onboarding process for new users in the Polkadot ecosystem.
- Increased adoption of decentralized applications in the Polkadot ecosystem.

#500 Unified Wallet And Dapp Interaction

No Active Proposals