Martin Kleppmann talk on local-first (LoFi)
1–10 of 28 posts
Re: Martin Kleppmann talk on local-first (LoFi)
#2This is the 1 year anniversary addition, and what a year of talk it's been. Lots of exciting stuff is happing in the world of local-first software this year, and this talk from Martin is the perfect way to kick it off!
If your new to all this, the term "Local-first software" originated from this Ink and Switch paper by Martin Kleppmann https://www.inkandswitch.com/local-first/
Re: Martin Kleppmann talk on local-first (LoFi)
#3So, you want to build an app that has its data co-located with its UI? That works offline? That synchronizes between clients? And that lets its users own their data?
Welcome to the world of local-first web development.
Re: Martin Kleppmann talk on local-first (LoFi)
#4Re: Martin Kleppmann talk on local-first (LoFi)
#5Re: Martin Kleppmann talk on local-first (LoFi)
#6LoFi is a thing already. It's an abbreviation of Low Fidelity.
Re: Martin Kleppmann talk on local-first (LoFi)
#7This event is the 1 year anniversary of the https://lofi.software meet-ups. It's great Discord community to join if you're interested in local-first software development.
Re: Martin Kleppmann talk on local-first (LoFi)
#8This event is the 1 year anniversary of the https://lofi.software meet-ups. It's great Discord community to join if you're interested in local-first software development.
I wouldn't be doing my job if I didn't query the wisdom of using Discord to celebrate local-first software dev ;)
I have a short list that I'm testing but none of them have the features we need: 1) Live video 2) # channels and 3) adoption
Even moving off Twitter has been a challenge but I am optimistic about bsky
Re: Martin Kleppmann talk on local-first (LoFi)
#9As for local first, I see it as a combination of a few things
- moving databases as close to users as possible [0]
- writing data without coordination with other nodes
- background sync
What this buys you is extremely high availability (as you can write without having to coordinate over a network), lower latency in general, because the database is right there (ideally within visual range), and more reliability, because network outages only effect background sync.
I'll also add that while local first is often seen in the context of b2c users, i.e someone using their smart phone while travelling on an urban train system that has network dead spots - I think the real use-case is industrial. A lot of facilities completely grind to a halt when there's a network outage, which is not that infrequent. To say nothing of in field and IoT applications in industries like agriculture and mining.
[0] the logical conclusion of "edge computing"
Re: Martin Kleppmann talk on local-first (LoFi)
#10This event is the 1 year anniversary of the https://lofi.software meet-ups. It's great Discord community to join if you're interested in local-first software development.