<aside> <img src="/icons/info-alternate_gray.svg" alt="/icons/info-alternate_gray.svg" width="40px" />
This document was created by Thomas R.
See his accounts on Twitter (X) and Polkadot forum.
</aside>
As a Community Manager, I deal with user issues, particularly those faced by newcomers exploring our ecosystem.
Being an experienced user, along with other teams in the ecosystem, it's easy to forget how challenging the onboarding journey can be. The learning curve is especially steep for users coming from EVM ecosystems, though Cosmos users tend to adapt more easily.
Users must navigate several challenges mentioned in the UX Bounty: multiple address formats, cross-chain transfers between Polkadot rollups and CEXs, and various unwritten rules (Existential Deposit, sufficient assets, Teleport feature, system chains) that aren't always clearly explained in the dapps they interact with. See Annex for users feedback.
YOU HAVE TO LEARN, and this learning process sometimes involves mistakes that can result in lost funds.
I witnessed users' challenges during Kusama's early days when dapps and teams were learning to prevent asset transfer mistakes by implementing warning messages. At that time, wallets were in their infancy—Polkadot.js was the only substrate wallet available, and it offered limited functionality, mainly for signing transactions.
As a result, dapps had to handle all risk mitigation features themselves.