Lesson 14 of 17 · All lessons

Section 5 · User Interface · 17% of exam

5.3 Use Lightning Components and Optimize Mobile UI

4 min read Updated Nov 19, 2026

Exam objective

Determine declarative options for incorporating Lightning components and describe programmatic customizations for Lightning components; select actions and layouts for Salesforce mobile.

Lightning pages are assembled from standard and custom components. Declarative options include adding standard components through Lightning App Builder, configuring component properties, using supported visibility filters, and adding components supplied by trusted packages. A custom Lightning Web Component can be made available for supported page targets by a developer and then placed by an administrator. The administrator decides page composition and activation; the component author controls its internal behavior. Understand that boundary when a scenario asks whether a builder can solve the need without code.

Programmatic Lightning components are built with Lightning Web Components or, in some legacy contexts, Aura components. They can provide tailored interactions, data presentation, and integrations beyond standard component configuration. Development requires expertise in component APIs, security, accessibility, testing, packaging, and deployment. A component should respect record access and avoid exposing data through client-side code. Use Lightning Data Service and supported framework capabilities where appropriate rather than inventing direct data-access patterns. Evaluate whether a standard component, flow, or configuration option is enough before requesting custom code.

Mobile optimization focuses on the actions and information needed while away from a desktop. Global actions support tasks without record context; object-specific actions support work tied to a record. Compact layouts surface key fields. Mobile navigation and page composition should prioritize frequent tasks and avoid desktop-only assumptions. Some components or custom behaviors may not be available or usable on every form factor. Verify current support for each component and test on actual mobile devices or the Salesforce mobile app.

Design for touch, readability, low cognitive load, and variable connectivity. Reduce unnecessary scrolling and make action labels clear. Use the right page layout and action layout for the mobile workflow, while preserving field-level and object-level security. The best mobile design is not simply a scaled-down desktop page; it is a deliberate task flow aligned with user context.

Applied scenario: Field technicians need to review a work record, capture a completion status, and attach a note from a phone. First check whether standard mobile pages, compact layouts, and a quick action or screen flow satisfy the task. If the flow requires a custom device interaction not available declaratively, define a custom Lightning component and have a developer verify mobile support, access, and offline behavior. Put the completion action near the record’s key information, keep the data entry short, and test with realistic screen sizes and field permissions. Design and risk review: A component’s presence in App Builder does not guarantee it works on every device or form factor. A package component may have its own license and permissions. Client-side code must not be treated as a security boundary. Avoid building a custom component when a flow or standard component can meet the requirement with lower maintenance. Mobile users may have intermittent connectivity, so verify which actions need a live connection and what happens when a save fails. Salesforce Certified Platform App Builder | SU ·26 guide alignment 23 Exam lens: First translate the stated requirement into a measurable outcome. Identify the actor, record or object in scope, timing, access boundary, and exception path. Eliminate choices that solve only the visible interface while missing the underlying data, security, or lifecycle requirement. Then compare the remaining supported features by fit, operational complexity, maintainability, and any dependency named in the scenario. A strong answer satisfies the stated need with the least fragile configuration and preserves the platform’s security and governance model. These are study heuristics, not additional official exam rules.

Extra concept: Treat configuration as a system rather than a list of settings. A field may participate in a formula, validation rule, flow, report, permission set, Lightning page, and deployment package at once. Before changing it, identify those dependencies, decide which are intentional, and test the full user journey. This dependency view explains why a locally correct change can still fail after deployment or for a different user. Use Setup dependency tools where available, source comparison, and focused regression checks; no single dependency view is guaranteed to reveal every runtime relationship.

Verification exercise: Turn the lesson scenario into a small test plan before calling the design complete. Record the starting data, the user permissions, the expected outcome, and the evidence that would confirm it. Test one ordinary path, one boundary condition, and one invalid or unauthorized path. Compare the result with the business requirement, then repeat after deployment in the target environment. This catches differences caused by data, activation, page assignment, sharing, or dependencies. Save the test cases with the release notes so another administrator can reproduce the result.

Key takeaways

  • Determine declarative options for incorporating Lightning components and describe programmatic customizations for Lightning components
  • Choose the platform feature that fits the requirement, data, access, and operating context.
  • Test realistic users, exceptions, dependencies, and lifecycle effects before release.
  • Official references: https://help.salesforce.com/s/articleView?id=005298964&language;=en_US&type;=1 https://trailhead.salesforce.com/content/learn/modules/lightning_app_builder https://trailhead.salesforce.com/content/learn/modules/lex_customization Salesforce Certified Platform App Builder
  • SU ·26 guide alignment 24

Check your knowledge

Answer exam-style User Interface questions with answers and explanations.

Practice User Interface
Finished this lesson? Mark it complete to track your progress.

Ready for the real exam?

Take the timed Platform App Builder simulator: same number of questions, same time limit.

Get Complete Access