Field Service Mobile App Builder
The Field Service Mobile App Builder is a Setup-based configurator for the Salesforce Field Service mobile app that technicians use on iOS and Android.
Definition
The Field Service Mobile App Builder is a Setup-based configurator for the Salesforce Field Service mobile app that technicians use on iOS and Android. The builder lets admins customize what each technician sees: which record screens, which fields, which actions, which Lightning components, which offline behaviors. The configuration deploys to the mobile app and changes the technician experience immediately on next sync. Branded buttons, custom forms, photo capture flows, signature workflows, and inventory lookups are all configured here.
Field Service Mobile App Builder sits in Setup, then Field Service Mobile, then App Configuration. It is the technician-facing counterpart to Field Service Settings (which configures dispatchers, work orders, scheduling). The mobile app uses Lightning Web Components for its UI surface; Mobile App Builder lets admins place, configure, and conditionally show components per technician profile or service territory.
What Field Service Mobile App Builder configures
Screen layouts and component placement
The builder lets you place Lightning components on the mobile app''s screens: Work Order, Service Appointment, Asset, Account, and so on. Drag fields, related lists, action buttons, custom LWCs onto the canvas. Each screen is a distinct configuration; technicians see what you place.
Field selection and form customization
Per record type, pick which fields display on the mobile app. Mobile screens have less real estate than desktop; the builder lets you trim to the most relevant fields per technician role. Form-style components handle multi-field entry with mobile-optimized inputs.
Quick actions and custom buttons
Quick Actions defined on objects appear in the mobile app''s action menu. The builder lets you pick which actions show on which screens. Custom buttons can trigger Flows, open URLs, or call custom LWCs. Common patterns: Capture Signature, Take Photo, Mark Complete, Add Parts.
Offline behavior
Field Service Mobile App is designed for offline operation: technicians often work in basements, remote sites, or areas without cell coverage. The builder configures which records sync offline (typically today''s appointments plus their related records), how often the app syncs when online, and which actions queue for later sync.
Branding and theming
The mobile app accepts branding: logo, color palette, font choices. The builder sets these per org; multi-brand orgs can configure per service territory. Branded apps feel like the company''s own product, not generic Salesforce.
Conditional component visibility
Components support visibility rules: show only for certain technician profiles, only for certain service territories, only when a record matches criteria. A premium-tier work order can show different fields and actions than a standard one; senior technicians can see audit information junior ones do not.
Custom Lightning Web Components in the mobile app
Custom LWCs targeting the lightning__FieldServiceMobile_DetailRecord or lightning__FieldServiceMobile_RecordEdit target work in the mobile app. Developers build LWCs once; the builder places them on relevant screens. This is how bespoke workflows (specialized inspection forms, complex pricing calculators) ship on the mobile app.
How to configure the Field Service Mobile App
Configuring the mobile app is a multi-step task: enable Mobile App settings, create app configurations, drag components onto screens, set offline policies, assign per-profile. Each step builds on the previous.
- Enable Field Service Mobile in Setup
Setup, then Field Service Mobile Settings. Enable the mobile app for the org. Confirm technician profiles have access to the relevant objects.
- Create or edit an App Configuration
Setup, then Field Service Mobile, then App Configurations. Create a new configuration or pick an existing one. Each configuration drives the mobile experience for a specific set of users.
- Customize record-page layouts
Inside the configuration, edit Work Order, Service Appointment, Asset layouts. Drag Lightning components, set field selection, add Quick Actions.
- Configure offline sync rules
Set which records sync offline (today plus tomorrow''s appointments, related records), sync frequency, and conflict resolution policy. Test offline behavior before rollout.
- Assign the configuration to profiles or territories
On the configuration, assign which profiles or service territories use this configuration. Different technician roles can have different mobile experiences.
- Test on real devices
Install the Field Service mobile app on iOS or Android. Log in as a technician with the relevant profile. Confirm the screens, actions, and offline behavior match expectations.
Place Lightning components, fields, related lists on each record page.
Object-defined actions surfaced in the mobile app''s action menu.
Developer-built components targeting Field Service mobile targets.
Which records sync, how often, conflict resolution.
Different configurations for different technician roles.
- Mobile screen real estate is limited. Trim aggressively; do not just port desktop layouts.
- Offline sync rules affect device storage. Excessive sync (everything for the next month) fills devices fast; tune for actual technician workflow.
- Custom LWCs need the right mobile targets in their meta XML. Components built for desktop will not show on mobile without the right configuration.
- App Configuration changes propagate on next sync. Technicians using the app may not see changes immediately if they are offline; communicate timing for major changes.
Trust & references
Straight from the source - Salesforce's reference material on Field Service Mobile App Builder.
- Field Service Mobile AdministrationSalesforce Help
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. Which Salesforce Cloud includes Field Service Mobile App Builder as a key feature?
Q2. What business function does Field Service Mobile App Builder primarily support?
Q3. How does Field Service Mobile App Builder help support agents be more productive?
Discussion
Loading discussion…