Kyle Mathews
@kam
New blog post on what I'm observing in the local-first world and where I think it's going. In short, I think it's a big upgrade for the web. It's giving me the same vibes as the React community circa 2014.
3 replies
0 recast
3 reactions
Kyle Mathews
@kam
We had tightly coupled web frameworks in the Rails/Django years and lost them with the shift to API-powered SPAs. At the heart of the local-first approach is database-grade sync technology—which will recouple our application stacks allowing for a new era of framework innovation.
1 reply
0 recast
0 reaction
Kyle Mathews
@kam
Local-first development is gaining steam as a new paradigm for building rich client apps. Allows syncing data to local DB for faster CRUD, simpler state management and built-in realtime/offline.
1 reply
0 recast
0 reaction
Kyle Mathews
@kam
Why now? Pioneers like Figma and Linear are showing how much better local-first products can be. A number of startups and open source projects are making their approach available to everyone.
1 reply
0 recast
0 reaction
Kyle Mathews
@kam
I think there's a good chance that the sync engines powering local-first will replace traditional APIs in rich client apps.
1 reply
0 recast
0 reaction
Kyle Mathews
@kam
Many issues to solve though before that can happen. I look in detail at one — how to do CRUD with CRDT-based Sync Engines (the most common approach). There's a very elegant solution with distributed state machines with nice advantages over traditional request/response models.
1 reply
0 recast
0 reaction
