How I built a local-first app for planning trips, and what I learned about the current state of the local-first ecosystem along the way.
Peter Van Hardenberg - Local First: the secret master plan
Local-first software: You own your data, in spite of the cloud
A new generation of collaborative software that allows users to retain ownership of their data.
but should apps see our data? - building [at] habitat
thinking small on the protocol
Local-First Software: Taking Back Control of Our Data | a mini-doc
Habitat's road to release: 04 Chalk - building [at] habitat
The one where we don't release an API :)
ATScience Ecosystem Map
An interactive map of research applications, infrastructure and communities built on AT Protocol.
microcosm: atproto building blocks
Open-source atproto services and resilient community infrastruture to launch your next app
calendar pt. 1: ATProtocol beyond AppViews - building [at] habitat
our approach to permissioned data (part 1!)
Call for Participation: AT Protocol Ecosystem Action Research - Ecosystem Action
A pilot program to facilitate cooperative, research-led innovation in the AT Protocol ecosystem.
Habitat's road to release: 07 bridging traditional SaaS apps - building [at] habitat
building bridges to the (organizational) atmosphere
calendar pt. 2: spaces, meet cliques! - building [at] habitat
permission-ed data without AppViews
Your ‘App’ Could Have Been a Webpage (so I fixed it for you…)
I was asked to install a mobile app to get access to the itinerary of a trip to Disneyland I'm taking with the kids. Fuck that noise: couldn't it have just been a Web page? An hour of reverse-engineering later, it is, and it's superior in virtually every way to the "app" that it replaces.
