Wow! You broke the record for adoption time of a new source database. Thanks for the feedback, and we're aware that this iteration is "fine but not great" 😬 We have some ideas around innovation: one of which is embedding the powersync service as a convex component. But that's a lot of work for us. Doing all that work would be justified if we see good uptake of this initial version in the Convex community. And you're the first uptake datapoint, so that helps :) We released this initial version to see whether "fine" can be good enough i.e. are people desperate for a solution that works offline. We'll see! 🍿

I have it working. Getting the WorkOS auth JWKS claims synced up with PowerSync expectations was a little bit finicky, but quickly resolved. Overall this is a fine solution and there is a decent chance I could run with it longer term. Fine but not great. I dislike that I need to split the brain of my project and PowerSync with convex does not seem to innovate on this much. It is the same gripe I have with any local-first solution that currently exists. TanStack DB, PowerSync, Electric, Replicache, even the more library-focused things like automerge or yjs are good, but convex has spoiled me. I don’t want to think about how to structure my data models. Or, at least if I do I want to just have controls at the TypeScript level for sync strategy, etc. Convex has spoiled me.

In the meantime, you could check out PowerSync: we shipped support for Convex today. The integration gives you offline first, optimistic updates and partial sync. LMK your thoughts if you decide to check it out. releases.powersync.com/annou…

In the aforementioned project, I had to be able to capture information offline or in low signal areas. I ended writing a lot of native code and then coming up with the sync logic myself. I was fighting turbo Native a lot but it would be easier now. With AI, it probably would be less drudgery writing the api layer but the sync logic was tricky. Since then, services like powersync have emerged which seems like a nice solution.

We shipped initial support for Convex as a source database. "Adding PowerSync to a Convex app gives you offline-first behavior, optimistic updates, and partial sync."

You can now layer powersync on top of convex for offline. Adds some complexity but if your use case really needs it then it's probably worth it

The tools that make this easier to build You don't have to build a sync engine from scratch RxDB: JavaScript database for web and mobile with built-in sync, conflict resolution, and offline support WatermelonDB: built specifically for React Native, uses SQLite, and is designed for thousands of records with complex queries PowerSync: syncs Postgres to local SQLite on mobile and web, handles the delta sync and conflict resolution layer for you Firebase Firestore: offline persistence baked in out of the box, handles sync automatically (with some limitations on conflict resolution) PouchDB: syncs with CouchDB, one of the oldest offline-first databases in the JavaScript ecosystem Pick based on your stack, your sync complexity, and how much control you need over conflict resolution.

plug: layer PowerSync on top of Supabase for a massive reduction in offline sync pain then you get true offline-first behavior, which firebase doesn't have

The team behind @powersync_ have been building devtools for over a decade, and all that experience enabled us drag our heels a bit when it came to dogfooding and in return we were able to move faster in other areas. We got there in the end though :) We're now dogfooding in the PowerSync Dashboard using powersync-js as well as our Drizzle and TanStack Query hooks. Syncing from MongoDB as a source database. This blog post describes that journey. Nice work by @Chriztiaan_dev and @Manrich121

zero, electric-sql tanstack db, powersync

We did the same thing recently, migrated the powersync[dot]com website to Tanstack Smooth sailing

PowerSync Dashboard quality of life addition: search your logs :)

If you use convex with powersync you can get optimistic creates and instant boot, if the added complexity is acceptable to you that is

In this fun video, Steven shows us how he created an experimental @MikroORM integration. For existing MikroORM users, PowerSync provides partial sync at scale: keep on-device SQLite synced with your backend database. PowerSync is designed for offline, real-time, and reactive use cases. For existing PowerSync users, you might want to check out MikroORM as another great option. From what we can tell, the latest version probably works on React Native and Web too.

We often speak to customers that are syncing massive (1GB ) volumes into SQLite This is something we'll have better support for over time, but a good workaround for now is to use the PowerSync SQLite Seeder community project

I considered powersync but couldn't find any integration with CoreData. I want to keep all local data in CoreData, it integrates with SwiftUI really nice.

Partial, consistent sync at scale is one of the hardest problems solved by PowerSync. We first launched with a declarative system called Sync Rules, which synced a user’s entire dataset to their device on first connect. This fell short in use cases where you didn't want to or need to sync everything up-front. So we built Sync Streams: a system where clients can still sync everything up front, or subscribe lazily to exactly what they need, when they need it, using parameters. Sync Streams has been soaking in the wild for the past few months and is now GA / Stable. Thanks to everyone who helped us put it through its paces.

PowerSync is proud to be sponsoring this year’s @stirtrek! And our own @devagrawal09 will be speaking on building Fast, Realtime, and Offline-First Apps with Sync Engines

6.) Local Sync (underrated, but powerful) Local-first apps store data on device → sync later. - Instant UI (no waiting on APIs) - Offline by default - Feels insanely fast Tools like PowerSync (not sponsored) make this easier: Sync server DB ↔ local SQLite automatically Still niche, but huge potential. I’m bullish on this, rarely see apps using it well.