Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[internal test]: UXUI feedback #40

Open
monica-tokamak opened this issue Oct 11, 2024 · 0 comments
Open

[internal test]: UXUI feedback #40

monica-tokamak opened this issue Oct 11, 2024 · 0 comments
Assignees
Labels
bug Something isn't working internal-test-simple-staking-v2.5 bug reports for simple staking v2.5 internal test

Comments

@monica-tokamak
Copy link

monica-tokamak commented Oct 11, 2024

Can you specify where the bug exists?

Stake

Which device are you seeing the problem on? (can select multiple)

Desktop

Which OS are you seeing the problem on? (can select multiple)

MacOS

What browsers are you seeing the problem on? (can select multiple)

Chrome

What happened?

  1. Commission Rate and Your Staked interval is close, making it less readable.
    스크린샷 2024-10-11 오후 2 00 56
    스크린샷 2024-10-11 오후 2 01 03

  2. Staking (where users perform staking-related transactions) and L2 (information verification) have different properties, so why did you combine them into a tab?
    To combine them despite their different properties
    L2 menu name should be renamed to L2 info
    스크린샷 2024-10-11 오후 2 01 28

  3. It's awkward to see “Available in wallet” before connecting wallet and after connecting wallet, even if you don't have TON balance.
    스크린샷 2024-10-11 오후 2 01 19
    스크린샷 2024-10-11 오후 2 15 34
    스크린샷 2024-10-11 오후 2 36 37

  4. symbol image
    스크린샷 2024-10-11 오후 2 04 16
    스크린샷 2024-10-11 오후 2 04 34

  5. It is confusing to see the network name in two lines.
    스크린샷 2024-10-11 오후 2 04 41

  6. I think it's better to use network symbols in common in the same service
    스크린샷 2024-10-11 오후 2 05 06
    스크린샷 2024-10-11 오후 2 05 09

  7. My transactions are disabled, so when I turned on the toggle, it changed to All transactions. UI that is not clear from the user's point of view.
    스크린샷 2024-10-11 오후 2 01 30
    스크린샷 2024-10-11 오후 3 51 02

  8. There are too many explanations. But it doesn't seem to be a necessary explanation.
    스크린샷 2024-10-11 오후 2 01 56

  9. The number of decimal places is too short.
    It need to show you the total number of digits (tooltip?)
    스크린샷 2024-10-11 오후 2 03 40

-The placement of the Restake function within the Withdraw tab lacks logical coherence.
Users typically expect to find related functions grouped together, so this arrangement doesn't align with the user's mental model.
-The Restake option, represented only by a toggle switch, is not visually prominent.
-It's not intuitive for users wanting to restake to have to check the Withdraw section.
-Having the Restake option on the same line as "Withdraw history" can be confusing for users and fails to clearly communicate the purpose of the feature.

스크린샷 2024-10-11 오후 2 07 35
스크린샷 2024-10-11 오후 8 17 13

  1. The "Withdraw history" label doesn't effectively communicate its purpose or content. When there's no history to display, Clearly state "No withdrawal history" or "You haven't made any withdrawals yet"
    스크린샷 2024-10-11 오후 2 08 48

  2. Button state inconsistency: The Unstake button is active even though the current balance (1.01 TON) is less than the entered amount (5 TON). This can be confusing for users. Visual indicators such as a red border around the input field or a warning icon should be added to provide immediate feedback to the user.
    스크린샷 2024-10-11 오후 8 26 52

  3. Despite performing the Unstake operation, the record is not reflected in the history. However, in some cases, the history is visible.
    스크린샷 2024-10-12 오전 10 55 57
    스크린샷 2024-10-12 오전 10 56 03

  4. The crucial information that Unstake must precede Withdraw is not immediately provided to the user, making it difficult for users to intuitively understand this process. Users who enter the Withdraw tab begin the process without clearly recognizing the necessity of Unstake, and only encounter this information belatedly through a warning message during the actual Unstake process.
    스크린샷 2024-10-12 오전 10 56 55
    스크린샷 2024-10-12 오전 11 00 45

Relevant log output

No response

Upload any screenshots to aid with explaining the bug.

Upload image here

@monica-tokamak monica-tokamak added bug Something isn't working internal-test-simple-staking-v2.5 bug reports for simple staking v2.5 internal test labels Oct 11, 2024
@monica-tokamak monica-tokamak changed the title [internal test]: UX feedback [internal test]: UXUI feedback Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working internal-test-simple-staking-v2.5 bug reports for simple staking v2.5 internal test
Projects
None yet
Development

No branches or pull requests

3 participants