Category: Salesforce

In addition to the 10 UX principles, there are many other UX design considerations. Taking a closer look at one of them, when building apps on Salesforce, it’s important to keep accessibility in mind as well.

Accessibility refers to the practice of making applications usable by everyone, regardless of their abilities.… Read the rest

The 10th and last UX heuristic is called Help and Documentation. It states, “It’s best if the system doesn’t need any additional explanation. However, it may be necessary to provide documentation to help users understand how to complete their tasks.”

There are two types of help.… Read the rest

The principle of Help Users Recognize, Diagnose, and Recover from Errors states, “Error messages should be expressed in plain language (no error codes), precisely indicate the problem, and constructively suggest a solution.”

To implement this principle,

• Use traditional error-message visuals, like bold, red text
• Tell users what went wrong in language they will understand – avoid technical jargon
• Offer users a solution, like a shortcut that can solve the error immediately

In terms of Salesforce, here are some specific scenarios.… Read the rest

The 8th heuristic, Aesthetic and Minimalist Design, states, “Interfaces should not contain information that is irrelevant or rarely needed. Every extra unit of information in an interface competes with the relevant units of information and diminishes their relative visibility”.

This translates to the following main points:

1. Each page should have a specific primary focus.

The Flexibility and Efficiency of Use principle states, “Shortcuts — hidden from novice users — may speed up the interaction for the expert user so that the design can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.”… Read the rest

The principle of Recognition Rather than Recall states, “Minimize the user’s memory load by making elements, actions, and options visible. The user should not have to remember information from one part of the interface to another. Information required to use the design should be visible or easily retrievable when needed”.… Read the rest

For the Error Prevention heuristic, it states, “Good error messages are important, but the best designs carefully prevent problems 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.”… Read the rest

The principle of “Consistency and Standards” states, “Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform and industry conventions.”

If you know me, you know I’m a HUGE fan of consistency. If the same thing has different names, formatting, or syntax, my eyes cannot unsee it.… Read the rest

The principle of User Control and Freedom states, “Users often perform actions by mistake. They need a clearly marked “emergency exit” to leave the unwanted action without having to go through an extended process.”

Fortunately, Salesforce already has some built-in mechanisms to support this.… Read the rest

The principle of Match Between the System and the Real World states, “The design should speak the users’ language. Use words, phrases, and concepts familiar to the user, rather than internal jargon. Follow real-world conventions, making information appear in a natural and logical order.”… Read the rest

The Visibility of System Status heuristics states, “The design should always keep users informed about what is going on, through appropriate feedback within a reasonable amount of time.”

Here are some examples of how to apply this principle to Salesforce:

• Showing the record’s path at the top of the record page.

In 1994, Jakob Nielsen of the Nielsen Norman Group wrote 10 general principles for interaction design. These principles are called “heuristics” because they are broad rules. They are not specific usability guidelines.

1. Visibility of System Status
2. Match Between the System and the Real World
3. User Control and Freedom
4. Consistency and Standards
5. Error Prevention
6. Recognition Rather than Recall
7. Flexibility and Efficiency of Use
8. Aesthetic and Minimalist Design
9. Help Users Recognize, Diagnose, and Recover from Errors
10. Help and Documentation

They apply today as much as they need back then, whether it’s to static .html… Read the rest

People have been using websites and web applications for decades. As such, they preconceived notions on how things should work.

For example, they identify buttons and links based on appearance, like rectangles and underlines, and know how they should behave before they interact with them.… Read the rest