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
General Considerations
Considerations for Field Service Mobile App
Base Components Support
Modules Support
Wire Adapters Support
Entity Support
Metadata and Custom Metadata Types Support
Offline Environment Details
Use Salesforce Features While Offline
Development Tools and Processes
Quick Start Tutorials
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Base Components Support

Base components are described in the Lightning Web Components Reference. All components are being reviewed for correct behavior in LWC Offline-enabled mobile apps.
The following table provides details for base components where support is incomplete or not available. Base components that are generally available but not listed here are supported.
  • Limited Support — Limited Support. Can be used, but has known (and possibly unknown) issues.
  • Not Supported— Not Supported. Doesn’t work, or shouldn’t be used.
Component Status Comments
lightning-combobox Limited Support Supported for use, but not mobile friendly.
lightning-datatable Not Supported This complex component was never designed for mobile use, and its behavior in mobile contexts is subject to change without notice.

See this post in the Trailblazer community for sample code for a simplified, mobile-friendly data table.
lightning-file-upload Not Supported
lightning-formatted-address Limited Support The static map feature only works in online mode. If a user is offline, an error message is displayed instead.
lightning-formatted-date-time Limited Support Supported for en-US locale only.
lightning-formatted-rich-text Limited Support URLs don’t open within a navigation view; external URLs work, but links to records don’t. Additionally, you can’t open any URL with a target="_blank" attribute.
lightning-formatted-time Limited Support Supported for en-US locale only.
lightning-formatted-url Limited Support URLs don’t open within a navigation view; external URLs work, but links to records don’t. Additionally, you can’t open any URL with a target="_blank" attribute.
lightning-input Limited Support Supported for en-US locale only.

Image uploading using the type="file" attribute isn’t supported. See Upload Photos from LWCs Using lightning-input Base Component in the Trailblazer community for additional details and a partial work-around.
lightning-input-address Limited Support The address lookup feature only works in online mode. If a user is offline, an error message is displayed instead.
lightning-input-rich-text Limited Support Associated components, lightning-rich-text-toolbar-button and lightning-rich-text-toolbar-button-group, aren’t supported.

Image uploading within a rich text field isn’t supported.
lightning-map Limited Support This component requires a connection to a mapping service, and can’t work while offline.

If users access this component while offline, an error message is displayed instead.
lightning-pill Limited Support URLs don’t open within a navigation view; external URLs work, but links to records don’t.
lightning-pill-container Limited Support URLs don’t open within a navigation view; external URLs work, but links to records don’t.
lightning-record-form Limited Support lightning-record-form doesn’t work with draft records, that is, records created while offline. See Considerations for getRecordUi for an explanation of the limitations.

Lookup fields are read-only.

Getters and setters aren’t supported in offline priming. In your custom components, make sure attributes passed to lightning-record-form are either hardcoded or have a simple API.
lightning-record-edit-form Limited Support lightning-record-edit-form doesn’t work with draft records, that is, records created while offline. See Considerations for getRecordUi for an explanation of the limitations.

Lookup fields are read-only.

Getters and setters aren’t supported in offline priming. In your custom components, make sure attributes passed to lightning-record-edit-form are either hardcoded or have a simple API.

If the input field isn’t on the page layout, you must pass the field in using optional-fields.
lightning-record-view-form Limited Support lightning-record-view-form doesn’t work with draft records, that is, records created while offline. See Considerations for getRecordUi for an explanation of the limitations.

Getters and setters aren’t supported in offline priming. In your custom components, make sure attributes passed to lightning-record-view-form are either hardcoded or have a simple API.

If the input field isn’t on the page layout, you must pass the field in using optional-fields.
lightning-tab Limited Support Supported for use, but not mobile friendly.
lightning-tabset Limited Support Supported for use, but not mobile friendly.
lightning-tree-grid Not Supported

Additional Component Considerations

Several localization and globalization issues affect a number of components. These issues generally affect formatting of dates, times, currencies, and numbers. They’re mostly irritating, but only cosmetic. However, a few can cause errors, most often due to incorrect processing of numbers with too many digits (15 or more digits) in them. If you encounter these, try rounding the number manually in JavaScript, to no more than 14 digits of precision, before passing it to a base component.

None of the lightningsnapin-* components are supported.