Pass the Salesforce Salesforce Designers User-Experience-Designer Questions and answers with CertsForce

 The two Salesforce features that should be suggested to improve the end-user experience are:

Favorite the often-used object. This feature allows the users to bookmark the object’s tab and access it quickly from the Favorites menu in the header. This way, the users do not have to search for the object in the App Launcher or switch to a different app to use it.

Personalize the navigation bar. This feature allows the users to customize the navigation bar in their Lightning app by adding, removing, or reordering the items. This way, the users can add the object they often use to their navigation bar and access it easily from any page in the app.

Accordion elements are UI components that allow users to expand and collapse sections of content. They are useful for organizing information in a limited space, such as on mobile devices. However, they also have some usability challenges, such as discoverability, accessibility, and navigation. To improve the usability of accordion elements in a mobile environment, two possible ways are:

Include persistent headings. Persistent headings are the labels that indicate the content of each section and allow users to tap on them to expand or collapse the content. Persistent headings should be visible at all times, even when the content is expanded, so that users can easily see the context and switch between sections. Persistent headings should also be clear, concise, and descriptive, so that users can understand what each section contains and decide whether to explore it or not. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Mobile Design]

Only allow users to open one selection at a time. This means that when a user taps on a heading to expand a section, any other previously expanded section should automatically collapse. This prevents the content from becoming too long and overwhelming for the user, and also helps to maintain the focus and hierarchy of the information. It also reduces the need for scrolling and the risk of losing the position of the headings. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Mobile Design]

Nesting an accordion inside of another is not a good way to improve the usability of accordion elements in a mobile environment, because it creates a complex and confusing structure that is hard to navigate and understand. It also increases the cognitive load and the number of taps required for the user to access the information. Using the ‘back’ browser button to collapse content is also not a good way to improve the usability of accordion elements in a mobile environment, because it breaks the user’s expectation and the consistency of the UI. The ‘back’ browser button should be used to go back to the previous page or screen, not to collapse the content within the same page or screen. It also makes it difficult for the user to return to the expanded content if they want to. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Mobile Design] References: [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Mobile Design]

Quantitative research methodology should be used to measure the success and usability of a feature on Experience Cloud. Quantitative research involves collecting and analyzing numerical data that can be measured, compared, or statistically tested. Quantitative research can help answer questions such as:

How many users are using the feature?

How often are they using it?

How long does it take them to complete a task with the feature?

How satisfied are they with the feature?

How does the feature affect key performance indicators, such as conversion rates, retention rates, or revenue?

Quantitative research methods can include surveys, analytics, A/B testing, usability testing, and benchmarking. These methods can provide objective and reliable data that can be used to evaluate the impact and effectiveness of a feature on Experience Cloud.

Qualitative research methodology, on the other hand, involves collecting and analyzing non-numerical data that can reveal users’ attitudes, behaviors, motivations, and preferences. Qualitative research can help answer questions such as:

Why are users using or not using the feature?

What are their pain points, needs, and goals with the feature?

How do they feel about the feature?

What are their expectations and feedback for the feature?

How does the feature fit into their context and workflow?

Qualitative research methods can include interviews, focus groups, observations, diary studies, and card sorting. These methods can provide rich and detailed insights that can be used to understand the user experience and identify opportunities for improvement.

Both quantitative and qualitative research methods are valuable for UX design, but they serve different purposes and answer different types of questions. In this case, the UX designer wants to know if the feature was successful and track usability over time, which are questions that can be best answered by quantitative research methods.

Dynamic Actions are a feature that allows the UX Designer to customize the actions that appear on the Highlights panel of a Lightning record page based on criteria such as record status, user profile, or field value. This way, the UX Designer can declutter the Highlights panel and show only the relevant actions for each record. Dynamic Actions can be configured in the Lightning App Builder instead of the page layout editor, which gives more flexibility and control to the UX Designer. References:

Salesforce Dynamic Actions – Overview & Deep Dive Tutorial

Create Dynamic Actions in Lightning App Builder - Salesforce

Add Visibility Rules for Dynamic Pages - Trailhead

The best way to store the information of Cloud Kicks’ storage facilities in Salesforce is to use objects to represent storage facilities and fields to store facility details. This is because objects and fields in Salesforce are analogous to database tables and columns, respectively1. Each object contains a set of fields that store data values, and each record is an instance of an object1. Therefore, if Cloud Kicks wants to store the same information that they have in their Excel sheet, they can create a custom object called Storage Facility, and add fields for each detail that they want to track, such as location, capacity, inventory, and so on. Then, they can create records for each storage facility and populate the fields with the corresponding data. This way, they can store and manage their data in a structured and consistent way, and leverage the features and benefits of Salesforce, such as reports, dashboards, automation, and security23.

Using objects to represent facility details and fields to store storage facilities is not a valid option, as it does not make sense to use objects as data values. Objects are meant to represent entities or concepts, not attributes or properties1. Using objects to represent both storage facilities and facility details is also not a good option, as it would create unnecessary complexity and redundancy in the data model. Objects can be related to each other through various types of relationships, such as lookup, master-detail, or many-to-many4. However, in this case, there is no need to create a separate object for each facility detail, as they are not independent entities, but rather characteristics of the storage facilities. Creating a separate object for each detail would also require creating more fields, records, and relationships, which would increase the maintenance and storage costs, and reduce the performance and usability of the system5. References:

Learn All About Objects and Fields in Salesforce - Forcetalks

Mastering Salesforce CRM Administration - Packt Subscription

Overview of Salesforce Objects and Fields

Object Reference for the Salesforce Platform

Understand Custom & Standard Objects Unit | Salesforce Trailhead

Themes and branding allow Salesforce app developers to customize the look and feel of their apps to match their company’s branding and accessibility standards. One of the features of themes and branding is the ability to select a brand color, which is the primary color used for buttons, links, and highlights. Salesforce automatically generates a color palette based on the brand color, which includes accessible colors that meet the WCAG 2.1 contrast ratio guidelines. This ensures that the app is visually appealing and accessible to users with different color vision abilities. Developers can also customize other aspects of the theme, such as the logo, page background, and default font. References: [Themes and Branding Basics], [Accessibility in Salesforce]

To let its users know when a new feature is enabled or available with a short video explaining the new feature, the recommended solution is to use a docked prompt using In-App Guidance. In-App Guidance is a feature that allows the designer to create prompts and walkthroughs that guide users through new or complex tasks in Salesforce. A docked prompt is a type of prompt that appears at the bottom of the screen and can contain text, images, or videos. A docked prompt can be used to announce a new feature and provide a short video tutorial on how to use it. The designer can also set the conditions for when and how often the prompt should appear, and track the user engagement with the prompt. References: : In-App Guidance | Salesforce Help : UX Designer Certification Prep: Designing with In-App Guidance | Trailhead

 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

 Responsive design is a web design approach that aims to make web pages adapt to different screen sizes and resolutions, ensuring good usability and user experience across all devices. Some of the best practices for responsive design are:

Specify breakpoint sizes: Breakpoints are the points at which the layout of a web page changes based on the width of the viewport. For example, a web page may have a two-column layout on a desktop, a single-column layout on a tablet, and a stacked layout on a mobile phone. Specifying breakpoint sizes helps to create a fluid and flexible layout that responds to the device capabilities and user preferences. Breakpoints can be specified using media queries in CSS, which allow applying different styles depending on the media features, such as width, height, orientation, resolution, etc. For example:

@media (max-width: 600px) { /* Styles for screens that are 600px or smaller */ }

@media (min-width: 601px) and (max-width: 900px) { /* Styles for screens that are between 601px and 900px */ }

@media (min-width: 901px) { /* Styles for screens that are 901px or larger */ }

Minimize page weight: Page weight is the amount of data that a web page transfers to load on a browser. It includes the size of the HTML, CSS, JavaScript, images, fonts, and other resources that make up the web page. Minimizing page weight helps to improve the performance, speed, and user satisfaction of a web page, especially on mobile devices that may have limited bandwidth, battery, and processing power. Some of the ways to minimize page weight are:

Optimize images: Images are often the largest contributors to page weight, so it is important to optimize them for the web. This means choosing the right format, size, resolution, and compression level for each image, as well as using responsive images techniques, such as the srcset and sizes attributes, to deliver the most appropriate image for each device and screen size.

Implement caching: Caching is a technique that stores a copy of a web page or its resources on the browser or the server, so that they can be reused without having to be downloaded again. This reduces the amount of data that needs to be transferred and improves the loading time of a web page. Caching can be implemented using HTTP headers, such as Cache-Control and Expires, or using service workers, which are scripts that run in the background and intercept network requests.

Minify and concatenate files: Minification is a process that removes unnecessary characters, such as whitespace, comments, and formatting, from the code files, such as HTML, CSS, and JavaScript, to reduce their size. Concatenation is a process that combines multiple code files into one, to reduce the number of HTTP requests that the browser needs to make. Both minification and concatenation can help to reduce the page weight and improve the performance of a web page.

Use a content delivery network (CDN): A CDN is a network of servers that are distributed across different locations and regions, and that store and deliver copies of a web page or its resources to the users. A CDN can help to reduce the page weight and improve the speed of a web page by serving the content from the nearest server to the user, reducing the latency and bandwidth consumption.

The other two options, using separate URLs per device and utilizing pop-up windows, are not considered responsive design best practices, as they can create usability and accessibility issues for the users. Using separate URLs per device means creating different versions of a web page for different devices, such as example.com for desktop, m.example.com for mobile, and t.example.com for tablet. This approach can lead to inconsistent and fragmented user experiences, as well as duplicate content and SEO problems. Utilizing pop-up windows means creating new browser windows that open on top of the current web page, usually to display advertisements, notifications, or forms. This approach can be annoying and intrusive for the users, as well as difficult to close or navigate on small screens.

The usability of accordion elements in a mobile environment could be improved by expanding the first section by default. This is because it can provide the user with a clear indication of what kind of content is hidden in the accordion, and encourage them to explore the rest of the sections1. Expanding the first section by default can also reduce the user’s cognitive load, as they do not have to make a decision on which section to open first2. Moreover, expanding the first section by default can improve the accessibility of the accordion, as it can help screen reader users to understand the structure and purpose of the widget3.

Using the Back browser button to collapse content is not a good option, as it can confuse the user and break the expected browser behavior. The Back button is meant to navigate to the previous page, not to collapse an accordion section4. Using the Back button to collapse content can also create navigation issues, as the user might lose their current page or state4.

Moving an expanded section to the top of the screen is also not a good option, as it can disrupt the user’s spatial memory and orientation. Moving an expanded section to the top of the screen can change the order and position of the accordion sections, which can make it harder for the user to find and access the section they want5. It can also create a jarring and inconsistent user experience, as the user might not expect the content to move around the screen5.