3 ms·
This is a great article. I've been working on tooling related to local-first/offline-first for the last 10 years, and the benefits both for end-users and develo
by matharmin 3y ago
This is a great article. I've been working on tooling related to local-first/offline-first for the last 10 years, and the benefits both for end-users and developers are great.
The biggest benefit for developers that I've seen is that state management gets _much_ simpler when it is all handled by a local database. Just run queries directly on every app/page, with live queries if the framework supports it. No need for maintaining in-memory app state and propagating changes to the different parts, no need for caching and associated cache invalidation issues.
The caveat is that keeping the local database in sync with the server is not easy, and it's best to use other tooling for it. I'm working on PowerSync [1] myself, and ElectricSQL [2] also looks quite promising (both also mentioned in OP).
[1]: https://powersync.co https://powersync.co
[2]: https://electric-sql.com https://electric-sql.com
- rollcat 3y agoPowerSync looks cool. I would love it if it could also address the question of data sovereignty for individual users somewhere down the line. I know it's not a priority when you need the product to first hit the market, start competing, become profitable, etc but it would be such a breath of fresh air in a world where everything you think you own is actually rented.
- kobieps 3y ago[flagged]
- TRiG_Ireland 3y agoIs it a great article? I have to read several paragraphs before I can begin to piece together a vague idea of what it's talking about. Starting with a brief definition would massively improve it.