Visualforce Developer Guide

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
Introducing Visualforce
Tools for Visualforce Development
Getting a Quick Start with Visualforce
Customizing the Appearance and Output of Visualforce Pages
Standard Controllers
Standard List Controllers
Custom Controllers and Controller Extensions
Advanced Examples
Override Buttons, Links, and Tabs with Visualforce
Using Static Resources
Creating and Using Custom Components
Dynamic Visualforce Bindings
Dynamic Visualforce Components
Integrate Email with Visualforce
Visualforce Charting
Creating Maps with Visualforce
Render Flows with Visualforce
Templating with Visualforce
Developing Salesforce Apps with Visualforce
Salesforce Platform Development Process
Tell Me More: Where Visualforce Pages Can Appear in the Salesforce Mobile App
Guidelines and Best Practices
Sharing Visualforce Pages Between Mobile and Desktop
Excluding Visualforce Pages from Mobile or Desktop
Creating Visualforce Pages That Work in Mobile and Desktop
Choosing an Architecture for Visualforce Pages in the Salesforce Mobile App
Optimizing the Performance of Visualforce Pages in the Salesforce Mobile App
Visualforce Components and Features to Avoid in the Salesforce Mobile App
Known Visualforce Mobile Issues
Considerations and Limitations for Using Visualforce in the Salesforce Mobile App
Prepare a Support Request for Problems with Visualforce Pages in the Salesforce App
Choosing an Effective Page Layout
User Input and Interaction
Managing Navigation
Introduction to the Salesforce Lightning Design System
Using Visualforce Pages as Custom Actions
Performance Tuning for Visualforce Pages
Adding Visualforce to a Salesforce AppExchange App
Using JavaScript in Visualforce Pages
Communicating Across the DOM with Lightning Message Service
Visualforce Best Practices
Standard Visualforce Component Reference
Appendices
PDF

Considerations and Limitations for Using Visualforce in the Salesforce Mobile App

Visualforce allows developers to build sophisticated, custom user interfaces that can be hosted natively on the Lightning Platform. Visualforce is Salesforce’s tried and true model, giving developers access to data and robust tools and functionality. There are many benefits to using Visualforce in the Salesforce mobile app, but also some limitations.

Usability

  • Easy to implement for greater productivity.
  • Page-centric model naturally splits large applications into small, manageable pages.

Integration with the Salesforce Platform and Other Tools

  • Access to Salesforce’s rich metadata infrastructure.
  • The standard controller allows access to objects directly and via relationships without executing a single query.
  • Visualforce pages can act as containers for JavaScript or third-party frameworks, like AngularJS or React.

Customization

  • Standard tabs, custom object tabs, and list views that are overridden with a Visualforce page aren’t supported in the Salesforce mobile app. Mobile users see the default Salesforce page for the object instead.

Interactivity

  • Limited interactivity (aside from JavaScript functionality you add yourself).
  • Difficult to create an immersive user experience.

Speed

  • Higher latency, which degrades mobile performance.
  • Poor match for low-end or older mobiles devices with limited compute resources.
  • Visualforce processes markup tags on the Salesforce server, which can increase response time.

The one.app Container

In Salesforce Classic, Visualforce “owns” the page, the request, and the environment. Visualforce is the application container. But in the Salesforce mobile app and Lightning Experience, Visualforce runs inside an iframe that’s inside the larger /lightning container. If you’re used to developing in Salesforce Classic, using the one.app container requires a few adjustments, mainly scope and security considerations. For more information, see Understanding the Salesforce Mobile App Container.