|Available in: both Salesforce Classic and Lightning Experience|
|Free version available in: All editions except Database.com|
Full version available in: Performance, Unlimited, and Developer Editions, and for an extra cost in: Professional and Enterprise Editions
You can make web and Visualforce tabs available in the Salesforce Classic Mobile app. When you build the web tab or Visualforce tab, edit the tab properties and select the Salesforce Classic Mobile Ready checkbox to ensure that the web page or Visualforce page displays and functions properly on a mobile device. Selecting the checkbox adds the tab to the list of available tabs for your Salesforce Classic Mobile mobile configurations.
It is important to note that most mobile browsers have technical limitations concerning display size, scripts, processor speed, and network latency. Review the following considerations before mobilizing your web and Visualforce pages to ensure that they are compatible with mobile browsers.
Mobile Web Tab Considerations
Consider the following when defining a web tab that will be used in the Salesforce Classic Mobile
- The ability to mobilize web tabs is only available for BlackBerry and iPhone devices. If you mobilize a web tab, keep in mind that Android users can’t view the tab in Salesforce Classic Mobile.
- The minimum BlackBerry operating system requirement for web tabs is 4.3.
- The tab type must be URL. The mobile application can’t run S-controls.
- Before mobilizing a web tab, navigate to the target URL on one of your organization's mobile devices to verify that it works as expected in a mobile browser. In the event that your organization's device inventory includes phones with different operating systems—for example, both iPhones and BlackBerry smartphones—be sure to test on each type of device. If users can’t accomplish the necessary tasks on the web page from a mobile browser, do not mobilize the web tab.
Visualforce Mobile Tab Considerations
Consider the following when defining a mobile Visualforce
- Visualforce Mobile is only available for BlackBerry and iPhone. If you mobilize a Visualforce tab, keep in mind that Android users can’t view the tab in Salesforce Classic Mobile.
- The Salesforce Classic Mobile app can run on BlackBerry operating system versions 4.3 through 7.0. For optimum performance, however, Salesforce recommends running Visualforce Mobile on BlackBerry smartphones installed with at least version 6.0.
- Because the display size is limited on mobile browsers, we recommend redesigning the Visualforce page to optimize it for mobile users:
- Set the sidebar and showHeader attributes on the <apex:page> tag to false. Phones have small screens and limited processing power, so it is essential that the page suppresses the tab header and sidebar.
- Set the standardStylesheets attribute on the <apex:page> tag to false. The standard Salesforce style sheet causes pages to load slowly on the device. Additionally, most BlackBerry browsers older than the 6.0 OS can’t properly interpret CSS . The best approach to adding a style sheet to your page is to include a <style> section just below the <apex:page> component.
- Set the columns attribute on the <apex:pageBlockSection> component to 1. There is not enough room on a mobile device’s screen to display two columns, so specifying a one-column layout prevents fields from wrapping awkwardly on the page.
- Splash pages don’t display in the Salesforce Classic Mobile app.
- In the Salesforce Classic Mobile app, the Visualforce page is embedded in a tab, so you should avoid using tabs for navigation in mobile Visualforce pages.
- The embedded browser in the BlackBerry client application doesn’t have built-in navigation. If your Visualforce page is a wizard, you should provide navigation links that allow users to return to the previous page and advance to the next page.
- BlackBerry administrators should be aware that the download size setting on the BlackBerry Enterprise Server affects how much data can be pushed to the device. Check that the download size setting is appropriate, and be sure to test your Visualforce pages before deploying them to your Salesforce Classic Mobile users.
- User agent inspection can be executed in a custom controller to support multiple devices. You can do this by inspecting the appropriate result of the getHeaders() method on the current page reference.