Offline-First Architecture with Smart Synchronization

Design an offline-first architecture for [APP NAME], a [REACT NATIVE/FLUTTER] app used by [AUDIENCE] in [DESCRIBE THE CONNECTIVITY SCENARIO].\\\\\\\\n\\\\\\\\n**Operations that must work offline:**\\\\\\\\n1) [OPERATION 1: e.g., create inspection record with photos]\\\\\\\\n2) [OPERATION 2: e.g., query inspection history]\\\\\\\\n3) [OPERATION 3: e.g., edit existing records]\\\\\\\\n4) [OPERATION 4: e.g., view maps/dashboards]\\\\\\\\n\\\\\\\\n**1) Local Database:**\\\\\\\\n- DB choice: WatermelonDB vs. Realm vs. SQLite (expo-sqlite)\\\\\\\\n- Local database schema (tables, relationships, indexes)\\\\\\\\n- Migration strategy for schema updates\\\\\\\\n- File storage (images, documents) in local filesystem\\\\\\\\n- Storage limit and cleanup policy\\\\\\\\n\\\\\\\\n**2) Sync Queue:**\\\\\\\\n- Pending operations queue (FIFO)\\\\\\\\n- Operation structure: \\\\\\\\\\\\\\\\\\\\\\\`{ id, type, entity, payload, timestamp, retries }\\\\\\\\\\\\\\\\\\\\\\\`\\\\\\\\n- Queue persistence (survives app kill/restart)\\\\\\\\n- Prioritization: critical operations first\\\\\\\\n- Retry with exponential backoff\\\\\\\\n- Batch sync: group operations for efficiency\\\\\\\\n\\\\\\\\n**3) Synchronization Strategy:**\\\\\\\\n- Connectivity detection (NetInfo + polling)\\\\\\\\n- Automatic sync when connection returns\\\\\\\\n- Manual sync (pull-to-refresh)\\\\\\\\n- Background sync (if supported by OS)\\\\\\\\n- Partial sync: send deltas only (not full data)\\\\\\\\n- Payload compression for mobile data savings\\\\\\\\n\\\\\\\\n**4) Conflict Resolution:**\\\\\\\\n- Scenario: same record edited offline on 2 devices\\\\\\\\n- Strategy: Last-Write-Wins vs. automatic merge vs. prompt user\\\\\\\\n- Conflict detection: version vectors or timestamps\\\\\\\\n- Merge rules per field (e.g., text → merge, number → LWW)\\\\\\\\n- Log of resolved conflicts for audit\\\\\\\\n\\\\\\\\n**5) Offline UX:**\\\\\\\\n- Visual connectivity status indicator (discrete banner)\\\\\\\\n- \\\\\\\\