Why Local-First Software Needs Network Resilience
Source: jakelazaroff.com
The distinction between “local-only” and “local-first” is becoming a practical requirement rather than a theoretical nicety as developers build for unreliable connectivity and offline-first architectures—atproto’s federated model offers a concrete alternative to both walled-garden apps and purely centralized backends. Jake Lazaroff’s framing exposes the hidden infrastructure dependency in most software marketed as “decentralized”: true resilience means designing systems that function across network states (offline, intermittent, degraded) while maintaining data sync and user agency. This reframes the infrastructure debate from ideology (decentralization good, centralization bad) into engineering specifics: which systems actually remain functional when the network fails, and who controls recovery paths when it comes back online.