Headless 360Advancedofflinemobilesyncfield-service
Design offline-first mobile patterns with Salesforce sync
Real World Scenario
Field sales reps in rural areas need offline catalog browse and draft order creation syncing when connectivity returns.
Expected Answer
• Local SQLite cache of catalog subset assigned to rep territory
• Offline Mobile SDK or custom sync with conflict resolution rules
• Queue outbound mutations with idempotency keys replayed on reconnect
• Visual indicators for stale pricing requiring refresh before submit
• Compress initial sync payloads; delta sync for subsequent updates
• Test conflict scenarios: price change while offline draft exists
• Admin controls forcing minimum sync before order submission if policy requires
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Local SQLite cache of catalog subset assigned to rep territory. Offline Mobile SDK or custom sync with conflict resolution rules. Pick based on your integration pattern and team capability. Offline-first demands explicit conflict policy—last-write-wins is rarely acceptable for B2B pricing. Optimize for scale and operational observability.
Architect Perspective
Offline-first demands explicit conflict policy—last-write-wins is rarely acceptable for B2B pricing.