vbaranov
commented
5 years ago @gabitoesmiapodo Your proposal looks much better from UX perspective than the current modal window!
Some aspects, that I am worried about:
- For Dutch Auction we have no tiers. Thus, it will be always one row in the table - not so informative.
- It is hard to realize in such representation how much transactions at all and how much have already been successfully mined. In other words, the user doesn't know how far is to the end.
- If there are multiple tiers, transactions are not sequential from tier 1 to tier n, because, for example, the last transaction is the initialization of crowdsale and it relates logically to the 1st tier.
- From the current statistics of Token Wizard, only ~6% of crowdsales were whitelisted and ~29% had multiple tiers. Thus, in most cases, there will be only one row in the table in such representation.
Summarizing, I would suggest
- Extend info about tx in "Current transaction" field including tier name and tx purpose
- replace the bottom table to the slider with a percentage of successfully signed transactions with the bottom text like '5 of 7 txs have been successfully finished'.
What do you think, does it make sense?
gabitoesmiapodo
I'm not convinced about the way this information is displayed now for several reasons:
It's a lot of information crammed into one screen.
There are several things happening at the same time, it can be confusing. Sometimes the same element is used to display a status, or that an user action is required. It should be clear what an element does, or what it intends to do, and it should do only that.
It's not clear for the user that only tiers with a whitelist are included here (the user might think "I've created X amount of tiers, why am I only seeing a few tiers?")
Tiers' names aren't displayed, so if the user has several named tiers, he / she only sees Tier 1, Tier 3, etc. (which may even not be consecutive numbers, adding to the confusion).
The user can't cancel or leave this section if something goes wrong, or if they just want to do that.
Generally speaking It's not always clear what's going on (to me at least).
I'm attaching an UI / UX proposal to get rid of some (or all) these 'problems'.
In this case, each transaction gets its own "step" where we can see what's going on for that transaction only.
If there's user interaction needed (for example we need the user to confirm or reject a transaction in the wallet), it's clearly stated what the DApp expects the user to do.
Users can go back to check finished transactions, if they need to.
Tiers are grouped in a list.
It's possible to cancel all the transactions here if the user wants to, for whatever reason (of course there should be a confirmation for this explaining all the consequences of this action).
All of this is obviously open to discussion, but I think it's a start.