Joined May 2023
- Tweets 1,538
- Following 783
- Followers 2,177
- Likes 1,620
303 Photos and videos
PowerSync retweeted
Jun 10
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."
1
1
201
PowerSync retweeted
We got our @powersync_ dashboard rewrite blogpost out. It took a while but at least we got it out before Bun could get their rust port post out 😅. Good read by @Manrich121.
powersync.com/blog/rebuildin…
1
3
588
Jun 2
We did the same thing recently, migrated the powersync[dot]com website to Tanstack
Smooth sailing
Jun 2
Our warp[dot]dev site gets 10M visitors/year. We migrated the whole thing from a no-code editor back to code in just 3 weeks.
Very few hiccups, and SEO actually improved. Plus, the marketing team is free to use Warp to ship future changes
5
284
May 28
Kobie walks us through the new search functionality in the dashboard. Which features are we still missing?
1
245
May 27
Evidence of how Sync Streams solve partial sync at scale - in this case a user is syncing 5B rows in their backend database to millions of rows in SQLite
1
3
550
May 26
Self-managed Private Endpoints are now available:
- Connect your source database over private AWS networks
- Zero public internet exposure
- Fully self service - no need to contact support
releases.powersync.com/annou…
2
247
May 21
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.
1
3
5
785
May 19
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
1
3
264
May 19
Repo: github.com/powersync-communi…
The specific example is for React Native, but the approach generalizes to any of our supported SDKs
1
110
May 15
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.
1
5
505
May 14
Using our reactive watch queries, you don't need to build UI invalidation by hand. Available on all our SDKs.
Great article by @InfoWorld promoting sync as a paradigm
May 13
Kill the loading spinner with local-first data and reactive SQL
spr.ly/6012BBalT2
3
336
May 13
"Local-first is not offline-first."
This is a clear take on why the distinction matters, and includes a kind nod 🥰
✨ What does it really take to build local-first web apps in 2026? A grounded, experience-driven perspective for developers who’ve been doing this long enough to be skeptical of silver bullets: smashingmagazine.com/2026/05…
1
5
529
May 12
Persistence on the web in prod?
0%
IndexedDB
60%
OPFS
40%
🍿
10 votes • Final results
1
3
439
May 7
The new OPFSWriteAheadVFS for wa-sqlite not only brings concurrent reads to SQLite on the web, but also makes write transactions faster!
It does this by not insisting every commit hit the disk immediately. Instead of updating the main database file right away, it writes changes into side log files first. That is cheaper, so small write transactions finish much faster.
2
1
12
1,117
May 7
If the app needs stronger guarantees, it can turn durability back up with PRAGMA synchronous=FULL or EXTRA. Then the VFS flushes more aggressively so recent commits are much more likely to survive crashes, but write performance drops. In plain English: NORMAL/OFF = faster but may lose latest writes; FULL/EXTRA = safer but slower.
1
1
130