Settings sync
| Platform | Status | Where |
|---|---|---|
| iOS | done | vulture-ios/Packages/Preferences/Sources/Preferences/Preferences.swiftvulture-ios/Packages/Preferences/Sources/Preferences/SharedDefaults.swiftiCloud key-value store. |
| Android | done | vulture-android/data/prefsvulture-android/domain/syncusers/{uid}/settings/synced, per-key last-writer-wins. |
Behaviour
Section titled “Behaviour”- User-facing settings sync: units, sport and automatic detection, map style, display toggles, optimisation type, openAIP on or off, automatic updates, zone defaults, the flight declaration, FLARM settings and SkySight opacity.
- UI state (filters, sort, play speed, panel state) stays on the device.
Platform differences
Section titled “Platform differences”- iOS uses iCloud KVS and stores units and enums as indices. Android stores ids in
settings/syncedwith a value, timestamp and device per key. iOSVultureShowTrackmaps to two keys. - Android keeps values it has no screen for (zones, declaration, home base) and writes them back unchanged.
Related
Section titled “Related”- Cloud sync, Settings overview, Units
- Sync schema §2 (
settings/synced) - Persistence and settings §3