Skip to main content

Offline And Sync

Offline-first capture is a core product requirement for the mobile app.

Expectations​

  • users can capture insights without an active connection
  • local persistence happens first
  • sync retries when connectivity returns
  • reads should fall back to cached data when possible

High-risk areas​

  • auth state and session restoration
  • API client queue behavior
  • offline queue retry behavior
  • insight capture form state and recovery

Source repositories​

Detailed implementation docs live in the mobile repo and should be treated as canonical when code and site docs differ.

Key references:

  • docs/ARCHITECTURE.md
  • docs/KNOWN-ISSUES.md
  • docs/API-INTEGRATION.md

Editing rule​

Keep changes small in offline, sync, and auth flows unless there is a deliberate migration plan.