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.