What offline-first means for design tools

Three claims hiding in the phrase

The phrase offline-first is used for everything from a browser game to a notes app, and it is rarely defined. Stripped of the adjectives it hides three claims: the tool opens with no network, it keeps your work in a file that belongs to you, and syncing changes nothing you made.

A design tool can pass the first test and fail the second, because the interface is cached while the document lives on a server. It can pass the first two and fail the third, because a sync process rewrites the local copy with a version it considers newer. Neither failure is visible in a screenshot, which is why the phrase needs turning into questions.

The reason to care is the shape of your working life. Design work happens in places with bad signal: a workshop in a basement, a train, a hospital waiting room, a client site with one bar of reception. Tools that make the local copy the real one keep working there, and tools that make the server the real one turn those places into outages.

• Claim one: the editor starts and accepts edits with no network
• Claim two: the document is stored in a place you control
• Claim three: syncing does not overwrite or reshape your work

Note: Ask which of the three claims a tool actually satisfies. An honest answer saves more time than another feature comparison.

Test one: does it open offline

Run the test rather than reading about it. Open the tool once with a connection, build something small, then switch to airplane mode, close the app completely and open it again. If the editor loads and the document is there, claim one holds.

Watch for the partial result, the common one. The interface comes back, the document list is empty, and the tool offers to sign in. That is a cached shell with a server-side document: a working online tool, but not the one the label describes.

Also check whether the features you care about are in the cached part of the app. In Canvasola the 3D layer stack is fetched on first use rather than pre-cached, so a device that never opened it will not have the stack offline.

• Load it once with a connection before testing anything
• Airplane mode, close the app, reopen it from the icon
• An empty document list means the document was never local
• Check that the specific features you need are cached too

Note: A test that passes proves the setup works today, on that device. Storage can be cleared later, which is what the second test is about.

Test two: is the file yours

The second test asks one question: where does the document actually live? The honest answers are a file on your disk, a storage area in your browser that you can export from, or a database on someone else's computer. Only the first two survive a bad connection.

The practical test is whether you can produce a file that another program can open. A proprietary format only the vendor reads is a lease, not ownership. An open format, such as OPML for a mind map or SVG for a drawing, lets you move the work without asking anyone, and a JSON project file means you can read it in a text editor. The backup guide covers the routine for that.

Canvasola keeps the current document in browser storage under canvasola_document_v2 and the workspace tabs under canvasola_workspace_tabs_v1, and it can write the project out as a .canv file, a JSON document with a CANV1 header carrying the canvas elements, the style, the mind map, the App Builder project and the camera.

• Ask which of the three places holds the document
• Export it and open the export in another program
• A JSON project file is readable without the vendor's app
• Canvasola project files can be up to 50 MB

Note: A browser storage area is not an archive, because it belongs to a profile that can be cleared at any time.

Test three: what does sync change

Sync is where local-first tools often stop being local. The question is not whether a tool syncs but what happens to your local copy while it does. Does a sync write over your file with a version from the server? Does it merge two versions and produce a third? Does it need an account?

There is a design choice hiding in each answer. A tool where sync is opt-in is promising that the local copy is the source of truth, because nothing leaves the device unless you ask. A tool where sync is automatic is promising something different, that the server is the source of truth. Both are fine, but they fail in opposite ways.

Ask the failure question too: what happens to the work if the sync fails halfway, the account is suspended or the free tier is shut down? A local-first tool has a good answer, because nothing happens, since the work was never on the server alone.

• Does sync overwrite, merge, or refuse to run on a conflict
• Is it opt-in, and does it need an account to be switched on
• Is the local copy the source of truth or a copy of it
• What survives if the sync fails or the account is closed

Note: A tool that cannot answer these questions is not broken, it is simply asking you to trust it, and trust is a poor substitute for a file.

Canvasola's model, described honestly

Canvasola is local-first with an optional cloud layer, and the local layer is the real one. Autosave writes to the browser as you work, under canvasola_document_v2 for the current document and canvasola_workspace_tabs_v1 for the workspace tabs, and nothing is uploaded unless you open the cloud panel yourself.

The optional tier is small and honest about it. A free account holds 5 cloud projects of 2 MB each, and a session lasts 30 days. The generous part is the local side and the file: a .canv project file is a portable JSON document of up to 50 MB, node images are capped at 1.5 MB each, and a document holds 5,000 elements with 20 versions of history.

The gaps are worth naming too. There is no live multi-user editing, so a shared document means exchanging files. Clearing site data or working in a private window can remove the local copy, which is why the project file is the part to keep. The browser's storage quota is not the app's to control. The offline guide sets out the three layers.

• Autosave is local, and cloud sync is opt-in
• The cloud tier holds 5 projects of 2 MB each, 30-day sessions
• A .canv file is a portable JSON document of up to 50 MB
• Node images are capped at 1.5 MB each

Note: The offline guide sets out the three layers, the cached app, the local autosave and the saved project file, and what each one protects.

Questions to ask before you switch

Switching tools is a decision about storage as much as about features, so ask the storage questions first. Where does the document live, and can I get it out? What is the file format, and can another tool open it? What is the size limit? Does the work need an account? What happens if I clear my browser data?

Then ask about the work itself. Which of your actual features are in the free tier? Does the tool store the file format you hand over to a client, or only a picture of it? Is there a print path, and does the export include a vector format? How do you move a project if you change your mind?

The offline mind mapping comparison applies these questions to mapping tools, and the complete Canvasola guide shows what the answers look like in this app.

• Where is the document, and can I get a file out of it
• Is the working format open, or is it a picture of the work
• Is an account or a network required for the features you need
• What happens to the work if the browser data is cleared

Note: Ask these of the tool you use now as well as the one you are considering, because the answer is sometimes better than you assumed.

A checklist you can reuse

• The tool opens and accepts edits with the network switched off
• The document is stored locally rather than only on a server
• An export can be opened in a program the vendor does not own
• It is clear whether sync is opt-in and what it overwrites
• The file format is known, with any size limit stated
• The project file can be saved, moved and reopened
• Clearing site data costs you a file you already hold

Common mistakes to avoid

• Reading offline-first as a feature. The phrase is a claim about storage, not a line on a feature list. Turn it into the three questions and run them before you move your work.
• Testing the app and ignoring the document. A cached editor with an empty document list is the usual partial result. Check that the file itself comes back, not only the interface.
• Assuming sync is a backup. A sync process that overwrites the local copy can remove work as easily as it preserves it. Know which side is the source of truth.
• Leaving the project file behind. The local copy lives in one browser profile. A .canv file is the copy that survives a new device, a cleared cache or a lost laptop.

Frequently asked questions

What does offline-first really mean?

It means three things at once: the tool opens with no network, it keeps your work in a file that belongs to you, and syncing does not change what you made. A tool can satisfy one of those and still carry the label.

Is a browser-based app really local-first if it runs in a browser?

It can be, and Canvasola is, because the work is written to local storage rather than to a server. The current document sits under canvasola_document_v2 and the workspace tabs under canvasola_workspace_tabs_v1, and cloud sync is opt-in.

How large can a Canvasola project file get?

A .canv project file can be up to 50 MB, and it carries the canvas elements, the style, the mind map, the App Builder project, the camera and the layout mode in one JSON document. Node images are capped at 1.5 MB each.

Does Canvasola sync automatically?

No. Autosave is local, and the cloud layer is something you switch on yourself with an account. A free account holds 5 cloud projects of 2 MB each and a session lasts 30 days, so work locally, save a .canv project file, and use the cloud only where it helps.

This guide is part of the offline and install collection. For the wider product tour, read the complete Canvasola guide, and keep the keyboard shortcut cheat sheet open while you work.