Salesforce Decode
Salesforcedecode
Back to questions
LWCArchitect (Hardest)offlinefield-servicemobile

Architect offline-first field service LWC with platform constraints

Real World Scenario

Technicians lose connectivity in rural areas; custom LWC work order checklist must allow data entry offline and sync when online.

Expected Answer

• Salesforce mobile offline primarily via Field Service mobile app patterns — custom LWC offline is limited • Evaluate Salesforce Mobile SDK or Field Service core flows before custom offline LWC • If hybrid: queue actions in IndexedDB with idempotency keys and sync service worker where platform allows • Conflict resolution strategy: server wins vs last-write vs manual merge • Clear UX for offline mode, pending sync count, and conflict errors • Do not store sensitive data in browser storage without encryption assessment • Pilot on real devices with airplane mode testing matrix

Follow-Up Questions & Answers

Click to expand — each follow-up includes a direct, interview-ready answer

Stay within limits by: Salesforce mobile offline primarily via Field Service mobile app patterns — custom LWC offline is limited. Bulkify everything — never query or DML in loops. If hybrid: queue actions in IndexedDB with idempotency keys and sync service worker where platform allows. True offline on Salesforce is a platform capability decision first — custom LWC cannot replicate FSL offline alone. Document the decision in an ADR and align with enterprise standards.

Architect Perspective

True offline on Salesforce is a platform capability decision first — custom LWC cannot replicate FSL offline alone.