runningamok

There is a lot of reason to be excited about local-first and how it could enable much lower costs to build useful apps (both in terms of money and skills). AI will certainly spur that on.

But I think local-first will be of the biggest benefit to small teams of professional developers who can see local opportunities bigger corporations are missing. At least in the short term.

There are barefoot developers too, but it's not as simple as professional vs barefoot — there's a spectrum of app developers, each with their own economic rationale.

Looks interesting! What are you using for peer-to-peer data sync?

I'm not sure exactly what you're seeing but I do see a trend of Postgres products focussed on the frontend app developer e.g. Supabase, Neon.

Those developers are used to dealing with objects and types and SQL is a step further removed from what they're comfortable with.

Agreed. Even better if it was a local-first web application.

Congrats! As a sheets user I appreciate that rows are seamlessly added as you scroll past the initial sheet size.

To what extent is data ownership/user control still a goal of local-first? It feels like that part of the rationale has tapered off.

One use case where SQLite is a good option is for embedding as a local database in an app. Starting local-only with SQLite allows you to defer a lot of the backend effort while testing an MVP.

My mistake, I see that post wasn't written by you

Clarification: I'm not the author of the linked post.

I read your post some time back and feel it's been an organizing force for developers in this space — great job and thanks for the work you put into it.

I often wonder about terminology. What was the reason you chose "local-first" over "offline-first" (or even "serverfree" as in this case)?