Salesforce Mobile App
The Salesforce Mobile App is the official iOS and Android app that gives users a mobile-optimized view of their Salesforce org.
Definition
The Salesforce Mobile App is the official iOS and Android app that gives users a mobile-optimized view of their Salesforce org. It is downloaded from the App Store or Google Play, authenticates to a Salesforce org, and presents a touch-friendly UI for accessing records, viewing reports, running approvals, and using most Lightning Experience features from a phone or tablet. Many Salesforce users spend a meaningful portion of their workday in the mobile app, especially field-sales reps, service technicians, and on-the-go executives.
The Mobile App is included free with every Salesforce license. It renders Lightning Experience pages with mobile-specific adaptations: touch targets, swipe gestures, scaled layouts, and offline support for the most common interactions. Admins configure mobile-specific behavior through Mobile Navigation menus, mobile-only Lightning pages (via Component Visibility on form factor), and the Salesforce Mobile Publisher product for organizations that want to deploy a branded, fully customized mobile app to App Store and Google Play under their own brand.
How the Salesforce Mobile App brings the platform to phones and tablets
Lightning Experience parity and the rendering model
The Salesforce Mobile App renders Lightning pages with mobile-specific adaptations. Standard Lightning Components render natively. Custom Lightning Web Components work too, provided they declare lightning__RecordPage or similar mobile targets in metadata. Some advanced UI patterns (deeply nested tabs, very dense data tables) render less elegantly on small screens. The mobile experience is best when admins design pages with mobile in mind, not just shrunk-down desktop layouts.
Mobile Navigation menus
Each user sees a mobile navigation menu configured by admin. Setup > Mobile Navigation > select a menu > add navigation items (objects, dashboards, Visualforce tabs, Apex tabs, External services). Multiple navigation menus support different user populations. The menu is a major UX lever because it controls what users can quickly reach; a cluttered menu reduces adoption, a curated one boosts it.
Form factor-based page design
Lightning App Builder supports per-form-factor page configurations. Build one record page for desktop, a different version for phone, optionally a third for tablet. Component Visibility rules can also conditionally hide components based on form factor (Show this component only when form factor equals Small). This is the mechanism for designing mobile experiences that feel native rather than awkwardly desktop-shrunk.
Offline support and Salesforce Mobile Offline
The Mobile App supports limited offline mode. Recently viewed records cache for offline reading. Some create-and-edit operations queue offline and sync when connectivity returns. Salesforce Mobile Offline is the more sophisticated offline product for field workers who genuinely operate disconnected: dedicated sync, conflict resolution, and configurable data priming. Field Service Lightning includes its own offline-optimized mobile app for service technicians.
Authentication and biometrics
Mobile authentication supports username/password with MFA, SAML SSO, OpenID Connect, and biometric unlock (Face ID, Touch ID, Android biometrics) for repeated sessions on the same device. Connected App configuration controls token lifetime and refresh behavior for mobile sessions. Salesforce Mobile Sessions can be longer-lived than web sessions for usability, but admins can shorten them for sensitive data scenarios.
Push notifications
The Mobile App supports push notifications to alert users about record changes, approval requests, mentions, and other in-platform events. Apex code or Process Builder/Flow can trigger custom notifications. Configure Notification Types in Setup, set the audience, and the platform handles delivery through Apple Push Notification Service and Firebase Cloud Messaging. Push notifications are the killer feature for time-sensitive workflows like approvals or service escalations.
Salesforce Mobile Publisher and branded apps
For organizations that want a fully branded mobile experience under their own brand (not Salesforce), Salesforce Mobile Publisher is the product. It produces a custom-branded iOS and Android app published to the App Store and Google Play under the customer''s developer account. The app contains the customer''s Salesforce content but appears as their own product. This is common for ISVs delivering Salesforce-powered apps to end users who should not see Salesforce branding.
How to configure the Salesforce Mobile App
Configuring the Salesforce Mobile App for an org is mostly about three things: which records and pages users can reach (navigation), how those pages look on phones (mobile-specific page design), and what users get notified about (push notifications). The work scales with the depth of mobile workflows the team plans to use.
- Confirm mobile use cases and user populations
Which users need mobile access? Field-sales reps need full mobile pipelines. Service technicians need Case management and offline. Executives need dashboards and approvals. Document the use cases to drive every config decision.
- Build the mobile navigation menu
Setup > Mobile Navigation > New. Add the items the audience needs: Accounts, Opportunities, Today (calendar), Dashboards, custom Lightning components. Multiple menus support different user populations.
- Design mobile-specific Lightning pages
For record pages where mobile experience matters, build a phone form-factor version in Lightning App Builder. Reorder fields for mobile priority, hide desktop-only components, simplify the related-list set.
- Configure push notifications
Setup > Notification Builder. Define notification types for important events: approval requests, Case escalations, opportunity stage changes. Set the audience per notification type. Test delivery on real devices.
- Configure mobile session policies
Setup > Session Settings > Mobile-specific settings. Adjust session timeout, biometric unlock, and refresh token lifetime for mobile use cases. Mobile sessions can be longer than web sessions for usability if data sensitivity allows.
- Enable biometric login if appropriate
The Connected App for the Salesforce Mobile App supports biometric login via Face ID, Touch ID, or Android biometrics. Enable for user populations that benefit from frictionless repeated login on personal devices.
- Test on real iOS and Android devices
Emulators are not enough. Test the actual user experience on common iOS and Android devices the user base actually uses. Check page render speed, touch targets, and offline sync behavior.
- Train users and roll out
Mobile adoption is driven by user familiarity. Train users on the mobile experience, share the App Store and Google Play links, and provide a quick-start guide. Track adoption via login history filtered to mobile clients.
Curated list of items users can quickly reach. Build different menus for different audiences.
Mobile-optimized record page in Lightning App Builder. Built separately from the desktop version.
Configurable notifications for record changes, approvals, mentions, and custom events.
- Lightning components without mobile target declarations do not appear in mobile App Builder. The metadata file needs the appropriate target (lightning__RecordPage, lightning__AppPage) for mobile rendering.
- Offline support is limited in the standard Mobile App. Genuine offline workflows need Salesforce Mobile Offline or Field Service Lightning Mobile, not the base app.
- Push notifications require Connected App configuration. Without the right scopes and Apple Push / Firebase setup, notifications silently fail to deliver.
- Mobile UX problems often stem from desktop-first page design. Pages with too many components, dense tables, and deeply nested tabs render poorly on phones. Design for mobile when mobile users matter.
- Mobile session policies inherit from org settings unless overridden. Tighten the policies for sensitive orgs; loosen for usability when the data risk allows.
Trust & references
Cross-checked against the following references.
- Salesforce Mobile App OverviewSalesforce Help
- Salesforce Mobile App FeaturesSalesforce Help
- Notification BuilderSalesforce Help
Straight from the source - Salesforce's reference material on Salesforce Mobile App.
- Set Up the Salesforce Mobile AppSalesforce Help
- Design for the Mobile AppSalesforce Help
- Salesforce Mobile PublisherSalesforce Help
Hands-on resources to go deeper on Salesforce Mobile App.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. How does Salesforce's multi-tenant model affect Salesforce Mobile App?
Q2. What architecture concept is Salesforce Mobile App an example of?
Q3. Who can benefit from understanding Salesforce Mobile App?
Discussion
Loading discussion…