Custom Home Pages
- Salesforce1 doesn’t support login redirection to Salesforce apps or custom home tabs like the full Salesforce site does. If you prefer to retain this redirection for users who log in to Salesforce from a mobile browser, turn off the Salesforce1 mobile browser app. This can be done on a user-by-user basis or for your entire organization.
Custom Actions and Buttons
- If you use URL custom buttons to pass parameters to standard pages in Salesforce Classic—such as pre-populating fields when creating a record—this behavior doesn’t work in Salesforce1 or Lightning Experience.
- Custom images used for action icons must be less than 1 MB in size.
- Standard tabs, custom object tabs, and list views that are overridden with a Visualforce page aren’t supported in Salesforce1. The Visualforce page is shown for full site users but Salesforce1 users will see the default Salesforce1 page for the object instead. This restriction exists to maintain the Salesforce1 experience for objects.
- Embedded Visualforce pages—that is, those added to a page layout—that contain an <apex:enhancedList> component may cause the Salesforce1 app to crash when used on iOS devices.
- When viewing Visualforce pages on an Android device, horizontal scrolling doesn’t work if the page is wider than the viewport. Redesign the page so that it’s narrower than the viewport.
- You can’t add more than 25 components to a Lightning Page region.
- These programmatic customizations to the UI aren’t supported: Web tabs and S-controls.