PranavNagrecha/AwesomeSalesforceSkills / skills/admin/fsl-mobile-app-setup
fsl-mobile-app-setup
VerifiedUse this skill when configuring, extending, or troubleshooting the Salesforce Field Service (FSL) Mobile app for field technicians — including offline priming strategy, app extensions, deep linking, and custom branding. Trigger keywords: FSL mobile, Field Service mobile app, offline priming, mobile extension toolkit, app extensions for field service. NOT for coding the LWC quick action or offline extension itself — use apex/fsl-mobile-app-extensions. NOT for technician job lifecycle, signature capture, or parts consumption — use admin/fsl-mobile-workflow-design.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.1 KB |
| references/examples.md | markdown | 7.0 KB |
| references/gotchas.md | markdown | 5.1 KB |
| references/llm-anti-patterns.md | markdown | 7.7 KB |
| references/well-architected.md | markdown | 5.1 KB |
| scripts/check_fsl_mobile_app_setup.pyexecutable | script | 6.8 KB |
| templates/fsl-mobile-app-setup-template.md | markdown | 4.5 KB |
references/well-architected.md
View on GitHub# Well-Architected Notes — FSL Mobile App Setup
## Relevant Pillars
- **Reliability** — The core challenge of FSL Mobile is ensuring technicians have access to the right data when they are offline and that data written offline is durably synced back to the org. Offline priming strategy, page reference budgets, and conflict resolution policies are all reliability concerns. A misconfigured priming setup results in technicians missing records mid-job with no recovery path until they regain connectivity.
- **Performance** — Priming sync time and device storage are constrained resources. Priming configurations that pull too many related lists or too wide a scheduling window increase sync time and device storage consumption. Poor performance in priming directly delays technician readiness, especially in environments with weak cellular coverage.
- **Security** — FSL Mobile downloads Salesforce records onto physical devices held by field workers. Devices can be lost or stolen. Security considerations include: ensuring mobile device management (MDM) policies are applied, confirming the FSL Mobile connected app enforces IP restrictions or MFA where required, and validating that offline data does not persist beyond the authorized session. Apex REST endpoints used by HTML5 extensions must enforce standard FLS and sharing rules — they do not inherit any mobile-specific security shortcut.
- **Operational Excellence** — FSL Mobile deployments require ongoing monitoring of priming health as data volumes grow. Teams should document the priming design, the page reference budget, and the extension architecture so future admins do not inadvertently add related lists that push the configuration over the silent 1,000-reference limit.
## Architectural Tradeoffs
**Priming window width vs. data completeness:** A wider scheduling window (e.g., 7 days) gives technicians more forward visibility but increases page reference counts and sync time. A narrow window (e.g., 1 day) keeps priming lean but means a technician who works early in the morning may not have afternoon appointments if the sync hasn't run yet. Choose the window based on technician work patterns and page reference budget.
**LWC Quick Action vs. HTML5 Extension Toolkit:** LWC actions are simpler, use LDS for offline data queuing, and are the strategic direction. HTML5 extensions offer lower-level DOM control and may be necessary for complex multi-step UI patterns or existing investments. New extensions should always start with LWC. Migrating existing HTML5 extensions carries risk unless there is budget and test coverage for the replacement.
**Custom branding vs. standard branding:** Custom branding through Mobile App Plus improves technician trust and app recognition, especially in white-label or partner scenarios. However, it requires an add-on license and republishing the connected app. Do not commit to custom branding in a project timeline without confirming the license is provisioned.
## Anti-Patterns
1. **Over-priming related lists without counting page references** — Adding every possible related list to the priming config in the name of "complete offline coverage" without tracking the total page reference count. This predictably exceeds the 1,000-reference limit in high-volume territories, producing silent record loss. Instead, audit page reference budgets before each new related list is added and enforce the 1,000 limit as a hard project constraint.
2. **Using the HTML5 Mobile Extension Toolkit for all new extensions** — Defaulting to the HTML5 toolkit because it was the only option in older FSL implementations, even for new development where LWC quick actions are fully capable. HTML5 extensions require Apex REST boilerplate, cannot use LDS, and do not benefit from platform offline data queuing. All new extensions should evaluate LWC quick actions first.
3. **Configuring FSL Mobile through the standard Salesforce Mobile surface** — Spending time building App Manager configurations, Briefcase rules, or standard mobile navigation expecting them to affect FSL Mobile. This produces no effect on FSL Mobile and delays actual delivery.
## Official Sources Used
- Field Service Mobile App — Field Service Developer Guide — https://developer.salesforce.com/docs/atlas.en-us.field_service_dev.meta/field_service_dev/fsl_mobile_intro.htm
- Create App Extensions — Salesforce Help — https://help.salesforce.com/s/articleView?id=sf.fs_mobile_app_extensions.htm
- Configure Deep Linking — Field Service Developer Guide — https://developer.salesforce.com/docs/atlas.en-us.field_service_dev.meta/field_service_dev/fsl_mobile_deep_links.htm
- Offline Priming — Salesforce Help — https://help.salesforce.com/s/articleView?id=sf.fs_mobile_offline_priming.htm
- Salesforce Well-Architected Overview — https://architect.salesforce.com/docs/architect/well-architected/guide/overview.html
- Object Reference — https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_concepts.htm
- Metadata API Developer Guide — https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_intro.htm
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |