This is one of the coolest things ever built.

It's shaping up to be an awesome crowd. Join us on July 1st in London!

Watch James Arthur 🦋 talk about Introducing TanStack DB. youtu.be/ia9FpY_Sw_4?si…

Excited to share a new starter for building apps with Expo, TANSTACK DB & ElectricSQL TanStack DB is nearing its first alpha so we're fine-tuning, writing docs, and building starters.

We're getting close to alpha, and it's looking really nice. We've found some very great abstractions and patterns that I think your going to love!

Starting in 15 mins

Signs your software is getting fast: you look up the keyboard shortcut for µ

incremental adoption ftw!

The “next React” won't be a framework. Sync engines are the next React. React replaced jQuery - yet their functionality barely intersects. In a similar way, sync solves some of React, and much of the most painful and poorly done libraries everyone uses.

Not long now! lu.ma/sync-london Talks are shaping up great and we’re well past venue capacity. Yonatan is airborn. Sam Willis has sorted out the pineapple cubes and cocktail sausages. If you’re in London on Tuesday and have been lurking so far, now’s your last chance!

Really looking forward to Sync London tomorrow! A bunch of exciting talks from teams building real apps on sync engines 🚀🥳

It's a PWA 🚀 We're so back!

Excited to release a new starter! Sync-first, production-ready, and blazing fast - TANSTACK Start - TANSTACK DB for blazing fast client-side queries & optimistic mutations - ElectricSQL for real-time sync from PG - Better Auth - Drizzle ORM - Tailwind CSS - Hono OpenAPI

Stop building real-time sync from scratch for AI apps 🧵 Just shipped an AI agent using sync engines instead of the usual WebSocket nightmare. Best decision I made this year.

Home for the next few weeks 😁 Love the 🏔️ in the summer!

Very excited for Tanstack DB as a “gateway drug” into local first sync engines. Respect the effort going into making it work with other sync engines and not just ElectricSQL 🫡💪

Two related, but separate ideas: 1. Local-first: An app that stores data locally, and works offline. 2. Sync-engine: Automatically syncing data between a web UI and a DB. These two ideas are often discussed under the umbrella term of "local-first". But that's unfortunate,

My first job was in an office with the bottom left most (half) window, designing medical devices. We had an incredible view of the chapel! The window above, a startup by Martin Porter, of the Porter Stemming algorithm, used by Postgres FTS via Snowball.

"Should my web app use a sync engine?" If your web app would benefit from caching, live queries, retries, instantaneous UX, offline support, streamlined state, then the real question is... "Why *wouldn't* I use a sync engine?"