Decide where the data belongs
Classify each input and output before choosing a provider. A local interface can still send information to a remote service; trace the actual route.
Check the offline boundary
Specify which functions must work without internet, which can queue work, and which must clearly stop. Test those conditions rather than relying on a product label.
Plan the machine lifecycle
Account for installation, runtime dependencies, storage, backups, updates, export, and uninstall. Local-first software still needs operations.
Use connections deliberately
Connect approved services for specific purposes. Keep credentials outside source, minimize permissions, and document how a connection can be revoked.
A concrete starting point.
For an offline design studio, theme exploration can remain available without internet while an optional publishing step clearly requires an authorized connection.
Your working checklist.
Mark what you have considered. This checklist stays on this page and is cleared when you reload.
Explore the related work.
General engineering guidance, not a certification, service agreement, or product-specific acceptance report.
Back to all field notes ↗