openwatersio / openwatersio/OpenWaters
Multi-device sync
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 1
- Avg merge
- 4h 22m
- Merged PRs (30d)
- 3
Description
Sync waypoints, routes, tracks, and settings across phone, tablet, and desktop.
Per docs/vision/design.md: local-first, sync when connected.
- Sync scope: markers, routes, tracks, vessel profile, settings, chart downloads (metadata only), instrument connection list
- Conflict resolution strategy (last-writer-wins vs CRDTs)
- Offline-first: sync is opportunistic, never blocks UI
- Account/auth model
- End-to-end encryption option
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading docs/vision/design.md and map the listed sync scope and constraints. A completed contribution would need an agreed design covering conflict resolution, offline behavior, account/auth, and optional end-to-end encryption; the issue does not name implementation files or tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop-dev, distributed-systems, mobile-dev, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100