keep-network / tbtc-dapp

Deposit BTC and redeem TBTC
http://dapp.test.tbtc.network/
MIT License
33 stars 31 forks source link

UX: TDT ID confusion risk in Mint / Redeem cycle #243

Open VVyvrn opened 4 years ago

VVyvrn commented 4 years ago

In current format there is high potential for confusion for users surrounding TDT ID. Consider current behavior:

1) the minting is completed, user is presented with TDT ID, i.e. : 0x3cAf685693B3e029e53D9C0e5EfE35691Cb5eE47

2) user holds tBTC until desired redemption time, returns to dAPP clicks redeem bond

3) Step 1 prompt for TBT ID and BTC address.... this is where user confusion could occur.

Imagine weeks or months have passed since minting, now the user wonders: "TBT ID, hmm, what is that? Is this my ETH wallet address? Wait, was there some number I was supposed to write down and remember it the whole time? Where do I look it up? How do I find that again if I don't remember?"

Suggested improvements:

1) popup / tooltip / link at Step 1 of Redeem explaining how to find this again if user doesn't remember.

2) description / link at end of Step 6 of minting, clarifying what the TBT ID is.

Again, think of users who don't really know the technical side. Will you have to remember this number? Is it tied to your ETH address? Can you find it in a contract? is it embedded in the tokens I have? Would it be a good idea to copy it down somewhere, like you might with a password or seed phrase?

I know we want a neat clean interface and don't want to overwhelm with info, but IMHO there has to be at least a link or something available for users who need more clarity on what this address is and what role it plays in the process.

Shadowfiend commented 4 years ago

This has less to do with wanting a clean interface and more to do with the dApp being an early stage alpha. We absolutely want to give users better tools for managing their deposits, and phasing the TDT id into the background instead of making it the primary user approach to referencing a deposit is a core part of that. You can see some early work in this department in #222.

Thanks for the detailed thoughts!