The offline cache works out of the box, but tuning it for your specific app makes a real difference. This article shows the controls.
Settings
- Total cache size: Maximum disk usage. Default 50MB; up to 500MB depending on user's device.
- Per-asset cache strategy: Cache-first, network-first, stale-while-revalidate.
- Cacheable API endpoints: Tick which endpoints' responses to keep.
- Cacheable datastores: Tick which list views and records get persisted.
- Pre-fetch on sync: Define what to fetch proactively (e.g. today's jobs every morning).
- Stale tolerance: How old before cached content is considered too stale.
Tuning by Use Case
- Read-heavy app: Aggressive caching, larger cap, longer stale tolerance.
- Real-time app: Light caching, short tolerance — fresh data matters.
- Mobile-bandwidth-conscious: Pre-fetch only on Wi-Fi; smaller cap.
- Field worker app: Pre-fetch today's work in the morning; expand cache cap; long stale tolerance.
Worked Examples
- Documentation site: Cache everything aggressively. Users frequently re-read articles.
- Live trading app: Cache nothing dynamic. Stale prices are worse than no prices.
- Field service: Pre-fetch each technician's jobs and customer addresses; cache route maps; tolerate 24-hour staleness for the customer's account history.
- Marketplace browser: Cache product images and recent search results; revalidate on every visit.