Salesforce1 Mobile App Developer Guide

Introduction
About This Book
Setting Up Your Work Environment
Salesforce1 Administration
Developing for Salesforce1
Welcome to Salesforce1 Platform Development
Designing Mobile-First User Interfaces
Extending Salesforce1 with Visualforce Pages
Adding Functionality with Visualforce Custom Actions
Integrating Your Web Applications in Salesforce1 with Force.com Canvas
Calling Quick Actions from the API
Extending the User Interface with Lightning Pages
Development Guidelines and Best Practices
When to Use the Navigation Menu or the Action Bar
Visualforce Guidelines and Best Practices
Sharing Visualforce Pages Between Mobile and Desktop
Excluding Visualforce Pages from Mobile or Desktop
Choosing an Architecture for Visualforce Pages in Salesforce1
Visualforce Components and Features to Avoid in Salesforce1
Choosing an Effective Page Layout
User Input and Interaction
Managing Navigation
Visual Design Considerations
Using Visualforce Pages as Custom Actions
Creating Visualforce Pages That Work in Mobile and Desktop
Performance Tuning for Visualforce Pages
Force.com Canvas Guidelines and Best Practices
Learning More
PDF

Sharing Visualforce Pages Between Mobile and Desktop

You should revise Visualforce pages that appear in both the Salesforce1 mobile app and in the full Salesforce site to support both environments. This includes Visualforce pages used as custom actions, and Visualforce pages added to standard page layouts, except those added to the Mobile Cards section of a page layout.

Visualforce pages that need to work in both environments include:

  • Pages used as custom actions. Custom actions appear in the action bar in the Salesforce1 mobile app, and in the publisher menu in the full Salesforce site.
  • Pages added to normal page layouts, when Available for Salesforce mobile apps is enabled for the page.
  • Custom Visualforce buttons or links added to normal page layouts.
  • Standard button overrides with Visualforce pages for the New, Edit, View, Delete, and Clone actions. Overriding standard list and tab controls isn’t supported in Salesforce1. Button overrides won’t appear in the Salesforce1 app unless Available for Salesforce mobile apps is enabled for the page.

    Standard buttons that are overridden with a Visualforce page disappear from record detail pages and record lists in Salesforce1 if Available for Salesforce mobile apps is disabled for the Visualforce page that overrides the corresponding button.

    Note