Mobile and Offline Developer Guide

Mobile App Development with Lightning Web Components and LWC Offline
Create Mobile-Ready Components
Use Mobile Device Features in Mobile Apps
Offline Considerations and Limitations
Offline Environment Details
What Happens When Something Isn’t Primed (Preloaded)
Create Components with Offline Analysis In Mind
Determine Online or Offline Status
Use Salesforce Features While Offline
Development Tools and Processes
Quick Start Tutorials
PDF

Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

What Happens When Something Isn’t Primed (Preloaded)

Priming for offline use is a “best effort” mechanism. Salesforce mobile apps are resilient in situations where resources are required by a mobile client but weren’t primed.
  • If the client is online, missing data and metadata resources are loaded when needed. There’s a minor performance impact due to the extra network requests.
  • If the client is offline, then missing data and metadata can’t be retrieved. The Lightning Web Components framework, and the Salesforce mobile app it’s running within, handle this situation with either a status display or an error message, depending on what wasn’t primed before going offline. Specific behavior is dependent on the component and how it’s implemented.