arcgis-kotlin-offline-workflows

Use this skill when the request involves offline GIS behavior in a Kotlin app.

Scope

• offline map areas
• mobile map packages
• local geodatabases or file-backed local content
• sync-enabled edits
• download, resume, retry, and refresh behavior
• storage strategy and content lifecycle

Workflow

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

Rules

• Do not treat offline support as only a download button; handle the lifecycle of local content.
• Surface progress and failure states clearly.
• Preserve local edits deliberately during sync flows.
• Watch for storage growth, stale packages, and background work assumptions.
• Prefer a small coordinator, repository, or view model for offline orchestration instead of burying everything in the composable.

Design checklist

Reference offline-workflow-checklist.md.

Example requests

• "Add offline map area download to this app."
• "Persist downloaded map content and reopen it on launch."
• "Implement sync for offline edits."
• "Diagnose why offline content is never refreshed."