How to work offline and install LiveNote as an app

Networks fail in the middle of things. The train goes into a tunnel, the café wifi drops, the airport hands you a captive portal, and the question that matters is simple: does the note you were typing survive? On LiveNote the answer is yes, and this guide explains exactly what happens, what you will see, and where the edges are.

Typing while offline

LiveNote saves as you type, and those saves do not depend on the network. While you type, edits are snapshotted into on-device storage in your browser (IndexedDB), so the page keeps accepting text whether or not the connection is up. The status chip in the header tells you which state you are in: when the connection drops it shows an offline state rather than pretending everything is fine.

• Keep typing. The editor does not lock or grey out. You write; the snapshots land on your device.
• Watch the chip. The status chip flips to an offline state, so you always know whether a save has left the building.
• Refresh with confidence. Reloading the page while offline restores your local copy, not an error screen.
• Reconnect and move on. When the connection comes back, pending edits sync automatically. There is no save button to hunt for.

When the server copy changed without you

There is one situation that deserves care. If you were offline for a while and someone else changed the note in the meantime, coming back online produces two versions of the truth: yours, snapshotted on the device, and the server’s current one. LiveNote does not quietly pick one for you.

If nobody touched the note while you were offline — which is the overwhelmingly common case — the reconnect is boring: your edits go up, the page is current, no banner appears.

Background Sync: saves that wait for you

In Chromium-based browsers there is a second layer. When a save cannot get through, the service worker registers a Background Sync request, and the browser replays that save when connectivity returns — even if you have already closed the tab. On browsers without Background Sync support the pending edits still go up the moment you reopen the page; the feature just covers the close-the-tab-first case.

Installing LiveNote as an app

Because the offline pieces live in a service worker, LiveNote can also be installed as an app rather than a tab. Chromium browsers do this from the browser menu — in Chrome the item is labelled “Install app” — and other browsers have their own install flows for web apps.

1. Open a note in the browser.
2. Open the browser menu and pick the install option — in Chrome it is labelled “Install app”.
3. Confirm, and LiveNote opens in its own window with its own icon, separate from your tabs.
4. Launch it from your dock, home screen, or start menu like any other app.

The installed app gets the same offline shell: the interface loads even with no connection, and note pages keep working on local snapshots as described above.

The honest limits

• Private browsing can block local storage. Some private-browsing modes restrict or wipe IndexedDB. When local storage is not available, the app tells you that local saving is unavailable and holds your edits in memory only — which survives until the tab closes and no further.
• Offline lives on note pages. The offline engine covers the editor. The shared-link view a reader sees is deliberately simpler and does not carry the same offline machinery.
• A conflict needs you. Autosave and Background Sync can move bytes, but only you can resolve the rare case of two divergent versions. That is deliberate: a machine guessing which words to keep would be worse.

The design goal was narrow: an interrupted connection should never cost you a sentence. It should cost you, at most, one decision when you come back.