Using Expo with real-time synced SQLite means that instead of having to: • manage network requests • handle loading states • implement retry logic • orchestrate state management between your local cache and remote data You just write queries™

wrote a whole blog post about this:

@expo I’ve been building with PowerSync for several months now. The hard part isn’t PowerSync itself, but the complexity of my needs: real-time sync, optional sync, local-first, offline mode, and Postgres as the server DB. Getting all this right is tough—PowerSync makes it easier.

@expo I really do not recommend SQLite for this. It can only have 1 write operation at the time and is just a file. Good for 1 device local database, not good for server use

@expo What’s the architecture of this like? I want to compare it in detail to @tan_stack DB.

@expo Ok, this is interesting, but what would “the best case” be for this feature?why would you need this over api ?

@expo Love the simplicity claim. Real measure is whether it actually saves time, not just marketing

@expo ok but how do you handle collisions?

@expo that's actually SO fast

@expo sorry gotta hate that modal backdrop sliding up with the modal instead of fading in/out

@expo Does this work inside Expo Go, or do we need a custom dev build to test the real time sync part? I know local SQLite works fine in Expo Go, but usually the sync features rely on native modules that aren’t bundled there

@expo Does it work with supabase?

@expo This is great!

@expo In One shot or several prompts?

@expo @grok what libraries would it needs, and on which version of Expo & React Native