arcgis-dotnet-offline-workflows

Use this skill when the request involves offline GIS behavior.

Scope

• offline map areas
• mobile map packages
• local geodatabases
• sync-enabled edits
• download, resume, retry, and refresh behavior
• storage and cache lifecycle decisions

Workflow

1. Determine which offline model the app needs:
   • packaged offline content
   • generated offline areas
   • sync-enabled editable data
2. Inspect how the app currently stores files, tracks jobs, and reports progress.
3. Fit ArcGIS jobs and sync operations into the app's existing async patterns.
4. Make status, cancellation, retry, and stale-data behavior explicit.
5. Keep local storage paths and cleanup rules predictable.

Rules

• Do not treat offline support as only a download button; handle the full lifecycle.
• Surface progress and failure states clearly.
• Preserve local edits deliberately during sync flows.
• Be careful with storage growth, cache invalidation, and update strategy.
• Prefer small services or coordinators for offline orchestration rather than burying everything in the page code-behind.

Design checklist

Reference offline-workflow-checklist.md.

Example requests

• "Add offline map area download to this field app."
• "Store map packages locally and reopen them on startup."
• "Implement sync for offline edits."
• "Diagnose why downloaded content never refreshes."