Replacing Amplify DataStore
Amplify Gen 2 does not support DataStore, and Gen 1 reaches end of life on May 1, 2027. A way to keep offline sync for a mobile app.
Amplify DataStore gave mobile apps offline-first sync on top of AWS AppSync. Amplify Gen 2 does not support it, and Amplify Gen 1 entered maintenance in May 2026, with its end of life on May 1, 2027. An app on DataStore needs another way to sync before then.
What DataStore did
It kept a local copy of the data, queued offline changes, synced them through AppSync when online, and resolved conflicts with a chosen strategy. Most personal-data apps used it for one thing: a person's records on all their devices.
Doing that with SyncPilled
- Local store: keep a database on the device (SwiftData or Core Data on iOS) instead of DataStore's.
- Sync: SyncPilled pushes local changes and pulls the rest, per person.
- Conflicts: the latest edit of a whole record wins. DataStore's default, Automerge, merged fields by type instead, so test the records your app edits on two devices at once when you migrate.
- Sign-in: any provider with a key set, Amazon Cognito included, as a custom issuer.
What it does not do
There is no GraphQL API, no data shared between people, and no server-side logic on records. If your app depends on those, AppSync without DataStore, or a full backend, fits better.
Replacing Realm Device Sync
MongoDB ended Atlas Device Sync on September 30, 2025. How to move a Realm app's sync to a small offline-first service.
Offline sync on Cloudflare Durable Objects
Why one SQLite Durable Object per person suits offline-first sync, and how SyncPilled orders, settles and stores each person's changes.