Local-first software treats the data copy on your device as a central part of how the application works. Cloud services can add synchronization or collaboration without participating in every basic operation.
For a productivity tool, the practical question is whether the task actually needs the content to be processed elsewhere.
Three tasks and their data routes
A JSON formatter can reorganize text in the browser. A text comparison can calculate differences on the device. A snippet can be stored locally and inserted without asking a server on every expansion.
Using the same content across devices does require data exchange. Different architectures are possible. FillKit offers optional ToolClack sync and optional Google Drive backup. Those features should not be described as if no data ever leaves the computer.
Local-first and offline-first are different
Offline-first describes the ability to keep working without a network. Local-first also concerns the role of the local copy, content availability and control over data.
The approaches can coexist. However, local processing in a browser does not automatically guarantee offline availability: a page may need to be loaded or an extension installed beforehand.
How FillKit applies this
Without an account, FillKit keeps snippets, autofill sets, details and settings in the browser. Its privacy policy states that this mode sends no telemetry to ToolClack.
With sync enabled, the browser keeps a usable copy and sends updates to the account. Offline edits synchronize when connectivity returns, as described in the sync documentation.
Benefits have limits
Fewer transfers can reduce latency and the amount of information held by the provider. They do not remove the risks of a shared device, an unprotected export or a lost browser profile.
Portability and backups therefore matter. FillKit supports exporting data: choose an appropriate location and check the contents before sharing the file. A local copy is not a complete recovery plan.
Does local-first guarantee better security?
No. Implementation, permissions and handling of copies also matter. It is an architectural choice, not a certification.
Why use the cloud at all?
For access across devices or collaboration, when those benefits are useful. The choice should be explicit and the data route understandable. See how these criteria apply to forms in the autofill privacy guide.
