Keep essential capability close to the user.
Local-first does not mean “never use the network.” It means ordinary use, user-owned state and essential guidance should not depend on a hosted service unless the feature genuinely requires one.
Why it matters
- Lower dependency on service availability for core workflows.
- Clearer ownership/export/deletion boundaries for user data.
- Reduced unnecessary transfer of private content.
- More predictable offline/recovery behavior.
- Less coupling between a release and mutable website prose.
Local content authority
Critical Help, Privacy/Terms snapshots, methodology, release guidance and troubleshooting can be packaged with software so the installed release remains self-explanatory. A website can still publish the latest public version, but it should not be the only place a user can understand the installed software.
Network features remain explicit
Fresh external data, store purchases, updates and configured providers may require network access. Those boundaries should be described by feature rather than hidden behind a broad “local-first” label.
Recovery and portability
User-directed export/backup is preferable to assuming a proprietary cloud is always present. Local-first systems still need clear corruption, migration, backup and device-loss strategies.