Study guide
9.4 Salesforce Mobile App Customization & Compact Layouts
Salesforce Certified Platform App Builder Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Platform Architecture, Boundaries & Extensions
1.1 Declarative vs. Programmatic Architecture & Limits 1.2 AppExchange Solutions & Package Selection 1.3 Core CRM Standard Objects & Capabilities
2 Chapter 2: Security, Access & Analytics
2.1 Object-Level & Field-Level Security 2.2 Record-Level Sharing Architecture 2.3 Advanced Sharing & Scoping Solutions 2.4 Reports, Custom Report Types & Dynamic Dashboards
3 Chapter 3: Data Model Architecture & Relationships
3.1 Custom Objects & Custom Field Types 3.2 Master-Detail & Lookup Relationships 3.3 Many-to-Many Relationships & Junction Objects 3.4 Schema Builder & Data Architecture Visualization
4 Chapter 4: Data Management & External Integrations
4.1 Field Type Conversions & Data Loss Considerations 4.2 Data Import Wizard vs. Data Loader 4.3 Salesforce Connect, External Objects & Indirect Lookups
5 Chapter 5: Declarative Formulas & Validation Rules
5.1 Cross-Object Formulas & Advanced Formula Functions 5.2 Roll-Up Summary Fields & Calculation Rules 5.3 Validation Rules & Error Handling Strategies
6 Chapter 6: Salesforce Flow Architecture & Design
6.1 Flow Fundamentals & Flow Trigger Types 6.2 Record-Triggered Flows: Fast Field Updates vs. Actions 6.3 Screen Flows & Guided User Interactions 6.4 Flow Execution Architecture, Bulkification & Fault Paths
7 Chapter 7: Complex Automation & Approval Processes
7.1 Multi-Step Approval Processes & Approver Routing 7.2 Approval Actions, Rejections & Record Locking 7.3 Automation Selection Strategy & Legacy Migration Patterns
8 Chapter 8: Lightning App Builder & Page Customization
8.1 Lightning Record, Home & App Pages 8.2 Standard, Custom & AppExchange Lightning Components 8.3 Custom Buttons, Web Links & Quick Actions
9 Chapter 9: Dynamic UI, Record Types & Mobile Experience
9.1 Dynamic Forms & Conditional Component Visibility 9.2 Dynamic Actions & Page Interaction Patterns 9.3 Record Types, Business Processes & Picklist Control 9.4 Salesforce Mobile App Customization & Compact Layouts
10 Chapter 10: Application Lifecycle Management & Sandboxes
10.1 Application Lifecycle Management (ALM) Stages & Governance 10.2 Sandbox Types, Capacity & Refresh Cycles 10.3 Sandbox Strategy for Development, Testing & Training
11 Chapter 11: Deployment Tools & Packaging Strategies
11.1 Inbound & Outbound Change Sets 11.2 Change Set Dependency Tracking & Deployment Sequencing 11.3 Managed vs. Unmanaged Packages & Distribution
12 Current Exam Blueprint, Agentforce & Flow Operations
12.1 Current Exam Facts, Official Weights & Study Mapping 12.2 AgentExchange: Extending an Org with the Agentforce Marketplace 12.3 Agentforce Automation for App Builders 12.4 Flow Approval Processes, Monitoring & Troubleshooting
9.4 Salesforce Mobile App Customization & Compact Layouts
Key Takeaways Explain This Topic AI
Compact Layouts control the key fields displayed at a glance in the mobile record header, desktop Highlights Panel, lookup hovers, and search result previews.
A compact layout can define up to ten fields. Current standard Highlights Panel documentation lists up to seven desktop fields and up to ten mobile fields; actual display depends on the enabled experience and space.
Compact Layouts support standard and custom fields of most data types, but explicitly exclude Long Text Area, Rich Text Area, and Multi-Select Picklist fields.
The Salesforce Mobile App navigation menu determines available navigation items, with the very first item in the menu functioning as the user's mobile landing page.
Object-Specific Quick Actions allow mobile users to create or update child records within the context of a parent record, supporting Predefined Field Values for streamlined mobile data entry.
Last updated: October 2026
9.4 Salesforce Mobile App Customization & Compact Layouts
Salesforce field representatives, traveling executives, and on-site service technicians rely extensively on the Salesforce Mobile App to manage customer interactions on smartphones and tablets. Because mobile devices operate under strict physical screen constraints and touch-driven interaction models, presenting dense desktop page layouts leads to poor user adoption, input errors, and operational delays.
A skilled Platform App Builder must design mobile-optimized experiences that deliver critical data at a glance and streamline high-frequency data entry. Achieving this requires configuring three core platform capabilities: Compact Layouts , the Mobile Navigation Menu , and Mobile Quick Actions .
Compact Layouts Architecture
A Compact Layout is a lightweight metadata definition that dictates which key fields appear in summary surfaces across Salesforce. When a user opens a record in the Salesforce Mobile App, the Compact Layout governs the Mobile Record Header —the prominent card pinned to the top of the mobile screen.
In addition to the mobile record header, Compact Layout fields appear in several key desktop and platform locations:
Desktop Highlights Panel : If Dynamic Forms or custom fields are not explicitly configured in App Builder, the Highlights Panel derives its display fields directly from the active Compact Layout.
Lookup Hover Cards : When a user hovers their cursor over a lookup link in Lightning Experience desktop, a floating card displays the fields defined on that object's compact layout.
Global Search Result Previews : Instant search dropdown previews and enhanced list hovers display compact layout fields.
Activity Timeline Cards : Key record summary data rendered within task and event timeline entries. [Salesforce Mobile Record View]
- ┌──────────────────────────────────────────────┐
- │ ACME Corporation │ ← Primary Field (Record Name)
- │ Type: Customer | Rating: Hot │ ← Secondary Field 1 & 2
- │ Phone: (555) 019-2834 | Annual Rev: $1.2M │ ← Secondary Field 3 & 4
- ├──────────────────────────────────────────────┤
- │ [Call] [Edit] [New Task] [New Opp] [▾] │ ← Mobile Action Bar
- ├──────────────────────────────────────────────┤
- │ Record Details / Dynamic Forms Sections │
- │ Related Lists / Activity Feed │
- └──────────────────────────────────────────────┘
- Compact Layout Definition and Display
Select up to ten fields in priority order. The first field is the primary identifier, usually Name or Case Number. Current standard Highlights Panel documentation lists up to seven fields on desktop and up to ten in the mobile app. Smaller surfaces and older mobile experiences can show fewer, so put the essential identifier, status, and contact details first and test the enabled mobile configuration. Do not memorize a universal primary-plus-four rule.
The newer Dynamic Highlights Panel has a separate field configuration in Lightning App Builder and depends on its mobile setting. Dynamic Forms alone does not change the regular Highlights Panel's compact-layout source.
Unsupported Data Types in Compact Layouts
Due to physical screen limitations and rendering performance, certain data types cannot be added to Compact Layouts :
- Text Area , Long Text Area (e.g., Description, Resolution Notes)
- Rich Text Area (e.g., Formatted HTML notes)
- Multi-Select Picklists
Eligible fields include standard Text, Number, Currency, Date, Date/Time, Lookup relationships, Formula fields, and single-select Picklists.
Compact Layout Assignments
Primary Compact Layout : The default compact layout assigned to the object across the entire organization.
Record Type Compact Layout Assignment : Administrators can assign different Compact Layouts to different Record Types . For example, an "Enterprise Opportunity" Record Type can display Total Contract Value and Executive Sponsor in its header, while a "Renewal Opportunity" Record Type displays Renewal Date and Churn Risk Score.
Salesforce Mobile App Navigation Menu
Administrators configure the mobile app navigation structure via Setup > Mobile App > Salesforce Navigation :
Navigation Menu Items : Administrators choose from available items—such as standard and custom objects, Visualforce tabs, Lightning Pages, Dashboards, and Tasks—and arrange them into the "Selected" items list.
The Landing Page Rule : The very first item in the Selected navigation list becomes the user's default landing page when they launch the mobile app. For example, if "Today's Tasks" is placed at position 1, the mobile app opens directly to the user's task list upon login.
Smart Search Items : If included in the menu, "Smart Search Items" automatically expands into a dynamic list of objects the user has recently accessed, ensuring easy navigation without manual configuration.
Lightning Apps on Mobile : For organizations utilizing modern Lightning Apps enabled for mobile, the mobile navigation menu automatically mirrors the navigation tabs defined on the corresponding desktop Lightning App.
Mobile Actions & Quick Actions Placement
Mobile users interact with workflows through the Mobile Action Bar , displayed prominently at the bottom of the screen (or docked in the header menu) in the Salesforce Mobile App.
Page Layout Action Configuration
To make actions visible on mobile devices, administrators navigate to the object's traditional Page Layout and locate the Salesforce Mobile and Lightning Experience Actions section:
By default, page layouts inherit global publisher actions.
Administrators click override the predefined actions to customize the specific list and sequence of mobile buttons.
The first 3 to 4 actions in this list appear directly on the mobile action bar; remaining actions are placed in the mobile overflow menu.
Global Actions vs. Object-Specific Actions on Mobile
- Action Dimension Global Quick Actions Object-Specific Quick Actions
- Invocation Surface Mobile "+" Global Action menu anywhere Pinned to specific record's Mobile Action Bar
- Record Context No relationship context to current record Full context; automatically links to parent record
Primary Use Case Fast standalone creation: Log a Call, New Lead Relational creation: New Child Contact on Account
Predefined Field Values Supported for static/user defaults Supported; can reference parent record fields
Tip
Predefined Field Values for Mobile Speed: Field technicians hate typing on virtual keyboards. On mobile Quick Actions, always configure Predefined Field Values . For example, when a technician creates a Work Order from an Account, use predefined values to automatically populate Priority = 'Normal' , Status = 'New' , and ContactId = Account.Primary_Contact__c . The technician can save the record with a single tap.
Desktop Highlights Panel vs. Mobile Header Comparison
UI Characteristic Desktop Highlights Panel Mobile Record Header
Primary Source Compact layout for regular panel; App Builder for Dynamic Highlights Depends on enabled regular/dynamic mobile panel
- Standard Highlights documented maximum Up to 7 fields Up to 10 fields; experience/space dependent
- Action Button Display Top-right header buttons + overflow ▾ Bottom docked Action Bar + overflow menu
- Field Wrap / Truncation Displays horizontally across page banner Stacks into responsive card format
- Unsupported Types Long/Rich Text, Multi-Select Picklists Long/Rich Text, Multi-Select Picklists
- Common Exam Traps and Best Practices
Trap: Assuming a universal field count. The layout can define ten fields, but each surface and enabled mobile experience controls display. Prioritize critical fields and test; the regular desktop Highlights Panel documents up to seven.
Trap: Using Global Actions for Child Record Creation. If an exam question asks how mobile users can quickly log a custom Inspection record linked to an Account, selecting a Global Action is incorrect. Global create actions do not automatically supply the active parent context; users may still select a parent explicitly. Always choose an Object-Specific Create Record Quick Action .
Trap: Attempting to Add Unsupported Fields to Compact Layouts. Never select Long Text Area, Rich Text Area, or Multi-Select Picklists when answering questions about compact layout optimization; Salesforce excludes them entirely from compact layout field pickers.
Best Practice: Distinct Compact Layouts per Record Type. Always configure distinct Compact Layouts for distinct Record Types when business needs dictate different operational metrics (e.g., Support Cases displaying Entitlement/SLA vs. Billing Cases displaying Invoiced Amount).
Official Source Check
Checked October 19, 2026: Current Highlights Panel documentation .