I'm sure whoever is developing the UI is experienced enough to know this, however since I'm studying it and been making a few exercises on UI evaluation I thought I should post this here because it could help members identify where we have most mistakes.
H2- 1 Visibility of system status
The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.
H2-2 Match between system and the real world
The system should speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.
H2-3 User control and freedom
Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.
H2-4Consistency and standards
Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.
H2-5Error prevention
Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.
H2-6Recognition rather than recall
Minimize the user's memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.
H2-7Flexibility and efficiency of use
Accelerators -- unseen by the novice user -- may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.
H2-8Aesthetic and minimalist design
Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.
H2-9 Help users recognize, diagnose, and recover from errors
Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.
H2-10 Help and documentation
Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large.
Some I can identify now:
H2-1
When I click on the account Tab, the last tab I was in is highlighted too. Ie. I'm at the "Trade" tab and click on my account. The "Trade" tab is still highlighted indicating me that I'm on the "trade" menu when I'm not. This means two tabs are highlighted. Am I at the my account menu or trade menu? Happens if I click on other tabs previously too.
When I'm at the "Explore" sub menus it doesnt state in which one I am at the moment. I can know where I am only if I read info on the page. Ie. Clicking on witnesses and seeing "Current witnesses" on small text at the top. If i'm not aware of that I dont know if I'm looking at a list of witnesses, committee members, etc. It's obvious for us, might not be for the average joe not familiar with the tech
H2-2
Uses terms for crypto users and traders which I guess are the ones using our system. Introduces a few new terms like witnesses, etc and that could be explained in the beggining maybe with a quick tutorial even though we have a "Help" button. Just a suggestion though, tutorials can be annoying too sometimes.
H2-3
No back or reload (even though I can control+r) buttons. Back button could be next to the "Account" one at the top. Refresh could be either there too or at the other side near the settings I guess.
H2-4
No consistency on the Withdrawal/Deposit menu. Each service has a different menu/set of options and layot. Looking at blocktrades comparing with the rest.
H2-5
Havent used the wallet enough to know this. I confirm you need to check each time you place an order. That's cool. Dont know if this happens too when you make a transaction to anyone.
H2-6
I think some people might confuse witnesses, committee members, etc so I think they could have a direct link on their page that redirects to the correspondent "Help" page or a pop up or something? Not sure about this as we dont want too much "noise" on the pages. Havent tested enough.
H2-7
Havent tested enough
H2-8
Seems fine I think
H2-9
Havent tested enough. This however could be more developed when creating an account. It's too confusing atm.
H2-10
Checks. Will be more developed with time.
Edit: I wanted to post this under the UI sub. Someone please move this. Sorry.
Topic: Jakob Nielsen's 10 Heuristics (Read 1755 times)
