This page is part of the User Experience Governance Initiative. It is also referenced in the ‣ section of the broader Polkadot 2.0 Strategy. These solutions are a response to ‣
- The Braille team Backlog with UX-related issues and solutions
- UX Studies and User Interviews to understand user requirements and expectations better
- Development of best practice guides and reference implementations
- Simplify token usage
- Tokens can live on several chains, confusing users.
- Providing UIs that can show possible routes to get to a destination could help users understand their options
- Providing simplified views could help casual users. This would force the heavy lifting of getting tokens where they are needed into the background
- Gas simplification: Users have to pay with numerous different gas tokens when using the ecosystem.
- Universal DOT acceptance: Push for making DOT a more universal payment token. This can be done by guiding parachain teams on how to configure the chain to allow DOT payments
- Gas abstraction: build parachain and client features that abstract away gas for the user and handle the sourcing of gas tokens under the hood
- Cross-chain multisigs: No practical solution has yet emerged to have cross-chain multisigs. What is necessary to get it done?
- Onboarding Experience: Users reported that there is not sufficient initial guidance for new users onboarding into the ecosystem
- User Manual: A handbook for the most common tasks in Polkadot was suggested. The Wiki serves that function but is more on the generic side. Specifically, guides have been asked for…
- Gamified Onboarding: Another proposal is to onboard users via a gamified experience
- Account abstraction: Allow more diverse ways for users to authenticate to their accounts
- Chain abstraction: Users have to use more and more frontends and chains to get use cases done. Abstracting away the complexity for users through APIs and more unified frontends would be helpful
- Create custom tooling for bounties (Tweet)
- Push the adoption of AssetHub by CEX integrators
- Support a universal Ledger app
- Develop clients and middleware templates that hide complexity from users
- Simplify Polkadot language - “parachains” could be “appchains”. “Collectives” could be “SubDAOs”