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.
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.
Wallet interaction should be familiar for users and provide a user experience that is replicated across all applications in the Polkadot ecosystem.
We would love to get your feedback on this proposal.
Find more details in the full proposal
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.
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.
Wallet interaction should be familiar for users and provide a user experience that is replicated across all applications in the Polkadot ecosystem.
We would love to get your feedback on this proposal.
Find more details in the full proposal
Threshold
Threshold