Add more sync options

[punchin-feedback]

Problem

I don't use Google or Microsoft or GitHub otherwise

Proposed solution

Add support for iCloud/Apple storage, Dropbox, maybe proton drive, nordlocker, or even a custom nas path or r2 or the like

Alternatives considered

No response

Scope notes

No response

[punchIn-app-bot]

Thanks for the suggestion — adding sync targets beyond Google/Microsoft/GitHub is a reasonable ask. Here's where each of your ideas lands after we looked at what's actually buildable.

How sync works today: each provider pairs an OAuth sign-in with the provider's own per-user storage, brokered through our Cloudflare Worker. A new backend is feasible when the provider exposes a usable per-user storage API that a browser app can reach.

Feasible to add

• Dropbox — the cleanest addition; it works almost exactly like the existing Google Drive / OneDrive flow (OAuth + an app-scoped folder). This would be the first one we'd reach for.
• Custom NAS via WebDAV (Synology, Nextcloud, etc.) — feasible and the only option here that needs no third-party account. Caveat: because the app runs in the browser, your NAS has to allow cross-origin (CORS) requests and be reachable over HTTPS — a plain http:// box on your LAN can't be reached from the installed app without extra setup.
• Cloudflare R2 / S3-compatible — feasible, but it needs a decision on how your storage credentials are held (kept in the browser vs. routed through a small relay), since these use long-lived keys rather than OAuth.

Not buildable (no usable public API)

• iCloud / Apple — Apple exposes no public API that lets a third-party web app read or write your iCloud Drive. (CloudKit only lets an app store data in its own container, not your Drive.)
• Proton Drive and NordLocker — neither offers a public developer API, so there's no supported way to integrate them.

Could you help us prioritize? Of the feasible ones — Dropbox, WebDAV/NAS, or R2 / S3-compatible — which would actually fit how you work? We'll line the work up accordingly.