Roadmap: iCloud sync and a public API
Updated Jul 12, 2026: named Boards, the built-in Pinned, Loved and Saved Boards, item reminders and time-based retention have moved out of this roadmap and into the local product.
Updated Jul 14, 2026: cross-device iCloud sync has also shipped — Mac and iPhone now share one memory. Mac App Store readiness and the public API are the two items still ahead.
We'd rather publish the plan and update it in public than leave an old promise pretending to describe today's app. Here is what is local now and what still comes next.
1. Shipped locally: Boards, reminders and retention
There is no longer one flat history. You can create named Boards; Pinned, Loved and Saved are created automatically; pin, heart, Save me and the four-square Board action are available on every item. Item reminders open the exact stored item from a local notification. Ordinary history expires after 30 days by default, with 60, 90, 120 days and Forever available in Settings. Pins, Board items and items with uncleared reminders are protected.
2. The full iOS interaction model
The iOS app now covers more than passive browsing: swipe left deletes, swipe right pins, a tap opens details, and a long-press exposes all item actions. It includes Pinned, Loved, Saved, custom Boards, reminders and safe opening for recognized web links. It still keeps its own local store in the current build.
3. Shipped: cross-device iCloud sync
Mac and iPhone now share one memory through a CloudKit private database scoped to your own Apple account. No SyncPocket App servers sit in the middle, and we can't see your history. The content hashes and stable item identifiers already used locally provide the reconciliation identity this layer needs.
4. Mac App Store readiness
Before a public release: App Sandbox, support for macOS 26 Tahoe's clipboard-privacy controls, distribution signing and the remaining store packaging work. None of this changes the memory model — it is the difference between a local development build and a one-click install.
5. A public API
This is the one we're most conservative about. Right now, the only integration surface is the documented, read-only on-disk format — and the honest current state is: there is no network API yet. We've published a draft anyway, because we'd rather have developers and future partners tell us what they need from it before we write the first line of server code, not after. If you're building a launcher plugin, an automation, or thinking about integrating SyncPocket App into something else, the API draft is where that conversation starts.
Why this order
The local model came first because Boards, reminders and retention had to behave correctly before two devices could reconcile them. Cross-device sync followed once that foundation was solid. The API remains last, deliberately, because a public API is a promise to keep.