These are sets of guidance on how to apply design principles to provide a positive user experience.
We can create space between elements, such as buttons, text, line separators, headers, and backgrounds, by leaving even space around them (either equal space or at most 1-pixel difference).
The dialog should either be “Close”, or “Cancel” and [ACTION_BUTTON], if the button placement is in the footer.
If there is one button on the bottom right, it should be “Close”. If there are two buttons, the first one on the left should be “Cancel” and the second one on the right should be an [ACTION_BUTTON], like “Save” or “Send Invitations”.
All buttons should have a visually definite emergence for the following states (if applicable):
d-disabled (greyed out or hidden)
When to use icons
a-When there’s not enough space for the label and an icon can easily represent the label.
b- It can help the user more quickly understand a feature.
When not to use icons
a- When the term/phrase is too specific or complicated.
It should be sentenced, one-line links should be fragments.
This text may be a title case or sentence case depending on its context.
a-If the tooltip is a noun, it should be a title case.
b-If they are declaring an action, then it should be a sentence case.
Usernames should be introduced by the @ icon in all places except for the Direct Messages list in the left-hand sidebar, and for any post or comment made by the user.
the username is as follows:
a- User list in the system console.
c- Members list for the current channel.
Error messages should:
a- State the come across problem with the component in the title.
b- To Give solutions for the next course of action.
c- To be consistent with the professional look.
d- To be avoided when possible (by avoiding the error condition).
Error messages should not:
a- Be in red or in capital letters.
b- Say or have the term “Error”.
c- Be lengthy.
d- Be generic.
e- End in an exclamation point.
Users would be able to enter information in the fields without any difficulties. The enter button on the last input field should trigger the default dialog button. All inputs such as text areas should behave consistently.
Items in a menu should be grouped based on the category they belong to.
It can appear as a dropdown bar from the top of the screen. The header bar:
a-May include an “x” button to dismiss.
b-Is limited to 60 characters.
c-May include a time-out.
d-Look over the rest of the UI instead of pushing the UI down.
e-Multiple headers can appear, with the prompt notification at the top and more recent notifications appearing covered.
UX Designers use guidelines to consider how to adopt principles such as impulsive, learnability, efficiency, and consistency so they can create compelling designs and meet and exceed user needs.
Follow the rules and Keep trying new UX design techniques and approaches to find the one that works the best for the user and their clients.
At Oodles ERP, we solve complex business problems by developing custom ERP solutions from the ground up. Our end-to-end ERP software development services enhance your business productivity with increased security, accessibility and operational efficiency. For more information, contact us at [email protected].