Mobile and Offline Developer Guide
jSummer '26 (API version 67.0)
Spring '26 (API version 66.0)
Winter '26 (API version 65.0)
Summer '25 (API version 64.0)
Spring '25 (API version 63.0)
Winter '25 (API version 62.0)
Summer '24 (API version 61.0)
Spring '24 (API version 60.0)
Winter '24 (API version 59.0)
Summer '23 (API version 58.0)
Spring '23 (API version 57.0)
Understand the Mobile Development Cycle
Debug Mobile Components
Prerequisites & Setup Considerations
Download and Install
Build a Briefcase
Select a Landing Page Template
Generate and Configure LWC Quick Actions
Deploy Your Configurations
Add LWC Quick Actions to Mobile Layouts
Newer Version Available
Configure the Offline Experience
In this section, we provide supplemental information on configuring your offline
experience.
For more detailed information, see about the Salesforce Offline App Onboarding Wizard Visual Studio Code Extension.
-
Build a Briefcase
Briefcase Builder is how you choose which records are available offline for your users. It's important to think about your users and which records they need access to while offline. The Offline App uses and depends on a Briefcase to use when priming records for offline use. -
Select a Landing Page Template
The Landing Page is the Mobile Offline home page for the Salesforce Mobile App. When a user logs into the Salesforce Mobile App offline experience, the landing page is the first thing they see. This page is intended to give access to the user’s most important records and allow them to quickly and easily take relevant actions. -
Generate and Configure LWC Quick Actions
The Onboarding Wizard can generate missing LWC quick actions based on the sObjects that are configured in your landing page template selection. -
Deploy Your Configurations
Before you can run a quick action based on a Lightning web component, you need to deploy the relevant code artifacts to your org. Components and quick actions can be deployed using the Onboarding Wizard or manually with Visual Studio Code. -
Add LWC Quick Actions to Mobile Layouts
For a quick action to appear in the action bar of a record view, it must be assigned to the main page layout for the record's object type.