Salesforce Docs Portal

Salesforce Customization: What’s Different or Not Available in the Salesforce Mobile App

Salesforce Customization: What’s Different or Not Available in the Salesforce Mobile App

Learn the differences between the Salesforce desktop site and the Salesforce mobile app.

Custom Home Pages

  • The Salesforce mobile app doesn’t support login redirection to other Salesforce apps or custom home tabs like the Salesforce desktop site does.
  • Avoid overriding the startURL in the login request. Because the startURL includes links to the redirect URI and approval page, overriding the startURL breaks the OAuth flow.

Custom Buttons and Links

  • Custom buttons that are added to the Button section of a page layout and that define the content source as URL or Visualforce are supported in the Salesforce mobile app. Remember that Visualforce pages must be enabled for use in the Salesforce mobile app.

    Custom links, custom buttons that are added to list views, and custom buttons that define the content source as OnClick JavaScript aren’t available in the Salesforce mobile app.

  • Using URL custom buttons to pass parameters to standard pages in Salesforce Classic—such as pre-populating fields when creating a record—doesn’t work in the Salesforce mobile app.
  • Custom images used for action icons must be less than 1 MB in size.

Custom Help

  • The Help Menu isn’t supported in the Salesforce mobile app.
  • In-App Guidance isn’t supported in the Salesforce mobile app.
  • The Guidance Center isn’t supported in the Salesforce mobile app.

Lightning Pages

  • Pull to refresh doesn’t work for custom Lightning web components in the Salesforce mobile app.
  • Changes that you make to Lightning record page assignments aren’t immediately reflected in the Salesforce mobile app. To see a newly assigned record page, close and restart the Salesforce mobile app.

Programmatic Customizations

  • These programmatic customizations to the UI aren’t supported: S-controls.
  • To improve performance, the Salesforce mobile app keeps previously viewed pages in memory. When a user goes back to a page or switches tabs, the app shows the page from memory instead of reloading it. As a result, the connectedCallback() lifecycle hook in a custom Lightning web component doesn’t run again when the user returns to the page.