Guides
How to test whether software really works offline
Test the exact build and platform without risking real data. A warm screen after airplane mode tells you almost nothing.
Scope: a concise editorial field note, not a universal recommendation, security audit, or guarantee.
Control the starting state
Prepare disposable data, quit fully, disable the network, and launch again. Do not rely on a session already in memory.
Blender documents no internet requirement for core use of its official build. That is a baseline for Blender, not a result for your app.
Finish a representative job
Use a disposable profile with representative data. Joplin documents a profile containing its database and resources, which is why the test should include search, an attachment, saving, quitting, and reopening.
When relevant, repeat with a throwaway account after signing out. Do not touch production credentials or data.
Reconnect and inspect
Reconnect and watch whether queued changes sync, fail, or request sign-in. Create conflicts only in disposable data and inspect the result.
Joplin documents sync targets and Syncthing device exchange. Neither proves your app’s conflict behavior, so record the test result.
Practical checklist
- Cold-start without a network.
- Create, edit, search, attach, save, and reopen.
- Test authentication with disposable state.
- Reconnect and inspect conflicts.
Sources checked
These first-party or authoritative sources ground the note. Checked 2026-08-14.