The two UX design principles that are key to creating excellent mobile user experiences are:

Consistency across device experiences. This means that the design of a mobile app or website should

match the design of the desktop version, as well as other platforms and devices. Consistency helps

users to recognize and trust the brand, as well as to navigate and use the product more

easily. Consistency also reduces the cognitive load and confusion for users who switch between

different devices12

Prioritization of content and UI elements on the screen. This means that the design of a mobile app

or website should focus on the most important and relevant information and actions for the user,

and eliminate or minimize the unnecessary or secondary ones. Prioritization helps users to achieve

their goals faster and more efficiently, as well as to avoid distractions and clutter. Prioritization also

improves the readability and usability of the product on smaller screens34

Reference: [Mobile UX Design: The Comprehensive Guide — updated 2023], [Mobile UX design

principles and best practices], [Mobile UX Design: The Ultimate Guide 2023 - Bluespace], [Mobile UX

Design: Key Principles. by Nick Babich - UX Planet]

https://uxcam.com/blog/mobile-ux/ https://uxplanet.org/mobile-ux-design-key-principlesdee1a632f9e6

An expert review is an activity that a designer can perform to conduct an independent audit of a

current website. An expert review is a method of evaluating the usability and user experience of a

website by applying established principles, guidelines, and heuristics. An expert review can help

identify the strengths and weaknesses of a website, as well as provide recommendations for

improvement. An expert review can be done by one or more experts, who can be internal or external

to the organization. An expert review can be done at any stage of the design process, but it is

especially useful before launching a new or redesigned website, or when there is a need to assess

the current state of a website. [UX Designer Certification Prep: User Research], [UX Designer

Certification Prep: User Testing and Evaluation]

Card sorting, task analysis, and prototype testing are not activities that a designer can perform to

conduct an independent audit of a current website. Card sorting is a method of organizing and

labeling information for a website, based on how users group and name the content. Task analysis is

a method of understanding and documenting the goals, tasks, and steps that users perform on a

website. Prototype testing is a method of evaluating the functionality and usability of a website by

having users interact with a mock-up or a simulation of the website. These methods are useful for

creating or improving a website, but they are not suitable for auditing a website without involving

the users. [UX Designer Certification Prep: User Research], [UX Designer Certification Prep: User

Testing and Evaluation] Reference: [UX Designer Certification Prep: User Research], [UX Designer

Certification Prep: User Testing and Evaluation]

The utility bar is a fixed footer that gives users quick access to productivity tools, such as notes,

history, and recent items. It can be customized for each Lightning app to enhance the user

experience and efficiency. Some of the standard use cases for using the utility bar are:

Perform common tasks without navigating away from the page: Users can use the utility bar to

perform tasks such as creating notes, logging calls, or sending emails without leaving their current

context. This reduces the need for switching tabs or opening new windows, and saves time and

clicks.

Access to view a list of records favorited for quick access: Users can use the utility bar to access their

favorites, which are records, lists, groups, or other items that they have marked with a star icon for

easy access. This allows users to quickly navigate to the items they use most frequently, and organize

them in a personalized way.

Access at any time to a customized set of items specific to an app: Users can use the utility bar to

access items that are relevant and useful for the app they are using. For example, in the Sales app,

users can access the Lightning Dialer, the Assistant, or the Today’s Events utility. In the Service app,

users can access the Omni-Channel, the Macros, or the Case Timer utility. The utility bar can be

configured to show different items for different apps, depending on the user’s needs and

p

.

Reference:

: User Experience Designer Certification Prep: Module 5: Design User Interfaces

: Lightning App Builder: Utility Bar

Confirmation bias is the tendency to seek out and prefer information that supports our preexisting

beliefs, while ignoring or rejecting information that contradicts them. Confirmation bias can affect

the validity and reliability of user feedback, as it can lead to biased questions, selective

interpretation, and skewed results. To avoid confirmation bias in user feedback, Cloud Kicks can

follow these two strategies:

Interview users about the intended use of the product to support the questionnaire creation. This

can help Cloud Kicks to understand the user needs, expectations, and goals, and to design questions

that are relevant, clear, and unbiased. By interviewing users, Cloud Kicks can also avoid making

assumptions about the user behavior, p

, and pain points, and instead base their questions

on real user data and insights 1.

Diversify feedback by ensuring it features as many unique perspectives as possible. This can help

Cloud Kicks to reduce the risk of sampling bias, which occurs when the feedback is collected from a

group of users that is not representative of the target population. By diversifying feedback, Cloud

Kicks can capture a wider range of user opinions, experiences, and feedback, and avoid overlooking

or dismissing important user segments or viewpoints 2.

Reference: [How to Avoid Confirmation Bias in UX Research]

(https://www.smashingmagazine.com/2017/10/avoid-bias-ux-feedback/), [How to Avoid Sampling

Bias in User Research] (https://bing.com/search?q=confirmation+bias+in+user+feedback)

The three considerations that should be made to improve the visual hierarchy of the page are:

Grouping proximity and common regions. This principle states that elements that are close together

or share a common boundary are perceived as belonging to the same group. This helps to create a

sense of order and organization on the page and reduce the visual clutter.

Scale using relative size to signal importance. This principle states that elements that are larger are

perceived as more important or prominent than elements that are smaller. This helps to create a

contrast and focus on the page and guide the user’s attention to the most relevant information.

Color and contrast, saturation between the elements. This principle states that elements that have

different colors or contrast levels are perceived as distinct or separate from each other. This helps to

create a variety and interest on the page and highlight the differences or similarities between the

elements.

Reference:

: Visual Hierarchy

: Gestalt Principles

Voice is the overall personality of the design, while tone is the way that personality is expressed.

Voice represents the core characteristics of a design, such as the values, attitude, and emotions it

conveys. Tone is how those characteristics are expressed in the design, suchas the language, visuals,

and other elements. For example, a design with a friendly voice might be expressed through warm

colors, friendly imagery, and casual language. Salesforce has some great resources on voice and tone

such as [1] and [2].

[1] https://www.salesforce.com/blog/2017/11/voice-tone-brandpersonality.html [2] https://www.salesforce.com/blog/2018/10/voice-tone-brand-personality-

ux.html

A wireframe prototype is a low-fidelity representation of the content and structure of a new feature,

without any visual design or branding elements. It is used to test the usability and functionality of

the feature with the user, and to gather feedback and iterate on the design. A wireframe prototype

can be created using tools like Sketch, Figma, or Adobe XD, and can be interactive or

static. Reference:

[Salesforce Certified User Experience Designer Exam Guide], Section 2.2: Design and test prototypes

[UX Designer Certification Prep: Prototyping], Unit 2: Wireframes and Prototypes

[Prepare for Your UX Designer Credential], Trailmix: Prototyping

The SLDS utility that provides the most flexible system to meet the requirements of designing a

responsive page is Grid. Grid is a utility that allows you to create a layout using a series of rows and

columns that house your content. Grid uses a 12-column structure that can be adjusted based on

breakpoints, which are predefined screen sizes that trigger a change in the layout. Grid also supports

nesting, alignment, ordering, and offsetting of the columns. By using Grid, you can create a

responsive page that can adapt to different screen resolutions and devices12 Reference: [Grid -

Lightning Design System], [Mastering Salesforce Lightning Design System Grids and Lightning

Layouts]

https://www.lightningdesignsystem.com/utilities/grid/

https://developer.salesforce.com/blogs/developer-relations/2017/04/mastering-salesforcelightning-design-system-grids-lightning-layouts

The development team missed two features that are causing the problems:

The With Sharing keyword in Apex classes to enforce sharing rules evaluation. This keyword allows

the Apex class to run in the context of the current user and respect the organization’s sharing rules.

Without this keyword, the Apex class runs in system mode and ignores the sharing rules, which can

result in unauthorized access to records that belong to other users .

The isAccessible() method in Apex classes to check field accessibility. This method returns true if the

current user has read access to the specified field, and false otherwise. Without this method, the

Apex class does not check the field-level security settings and can display fields that should be hidden

from the user, such as the shipment amount .

Reference:

: Using the with sharing or without sharing Keywords

: Enforcing Sharing Rules in Apex

: Schema.DescribeFieldResult Class

: Enforcing CRUD and FLS