Knowledge base › Tools

Journaling drops out precisely in the minutes that would suit it best: on a plane, on the underground, on a train, abroad with data switched off. Most apps at that moment either show a spinner or — worse — let you write and then lose the entry. This article shows the three different things that get called offline support, and how to find out in two minutes which one you got.

Why is this even a question

At first hearing it is an odd question in 2026 — there is network everywhere. In practice, the minutes that suit journaling overlap surprisingly often with the minutes without a network.

• On a plane, where there are two idle hours and neither calls nor notifications.
• On the underground and in tunnels, where the network flickers every few seconds.
• Abroad, where data roaming is switched off because it is expensive.
• A hike, a house in the country, a basement, a hospital waiting room — where the signal is one bar.
• In the evening, when you deliberately put the phone into airplane mode so it stays quiet.

The last one matters most and is mentioned least. People who take the evening close-down seriously usually switch the network off too — and if their app does not work then, the system stands in its own way at its best moment.

Three different things are called offline support

When an app says it “works offline”, that can mean three quite different things. It is worth knowing which one you got, because the difference shows up in your data.

1. Level one — nothing. The app is a website in a frame: without network you get a blank screen or endless loading. You can neither read nor write. This is the most common.
2. Level two — reading offline. Earlier entries are visible because they are on the device, but you cannot record a new one, or the save button does nothing. This is a half-solution: a journal is for reading, but you have to write when the event is fresh.
3. Level three — writing offline, with sync. You write, you save, and the entry is on the device immediately. When the network comes back, it goes up on its own. This is what offline support actually means.

Level three has a fourth tier that most apps do not solve: that not only writing but every function works — goals, habits, search, settings. Plenty of apps let you write offline, but the other pages are empty.

Five questions to ask any journal app

If it passed that test, five more things are worth settling. They typically do not appear on the marketing page, and all of them can be tried in ten minutes.

1. Does it work from a cold start? Does the app open after being fully closed in airplane mode, or only if it was already running?
2. Every page, or only writing? Check the goals, the earlier entries, the search. If those are empty, offline support is only partial.
3. Can you see what is waiting to upload? If the app does not show how many changes are still on the device, you are trusting it — you cannot check it.
4. What happens if you also wrote on another device? This is the most important and the least visible question. There is a separate section on it below.
5. What if there is no network for days? In some apps the local store fills up or overwrites after a handful of entries. A week of offline writing is a good test.

What exactly happens when there is no network

It helps to understand the mechanism, because it shows why the level you got matters. The order in a well-built system is always the same, and the point is in the first step.

1. The write goes to the device first. Not to the server but to the phone’s own storage — and the interface works from there. The network never stands in the way of entering data.
2. The change is marked. The system remembers what has not gone up yet. That mark survives closing the app and restarting the phone.
3. The upload runs separately. When there is a network, the marked changes go up. Ideally not only while the app happens to be open.
4. Up first, then down. Local changes go up first, and only then does what you did on another device come down. In the reverse order, a freshly written entry can be overwritten by an older state.

That fourth point causes most of the data loss in weakly built apps — and precisely because of that it is invisible in the interface. It only shows up if you use two devices.

When you wrote on two devices

This is the hardest question in offline support. Suppose you wrote on your phone on a plane in the morning while you also typed something on your computer at home — and in the evening both reconnect. Which one survives?

The bad answer is that the last one overwrites everything. That is the simplest implementation, and it is where the entry written on the plane disappears — apparently without trace. The good answer is that the system merges the two: what was created in one place does not delete what was created in the other.

This is hard to check from outside, but there is a simple trial. Write an entry on one device in airplane mode and another at the same time on the other device, then switch the network back on for both. If both entries are there, the system merges. If only one is, at least you know what to expect.

What is NOT possible offline — and why

For the sake of honesty: there is one thing that does not work without network, and it is not a question of implementation. AI features — the mentor’s replies, pattern recognition, generated summaries — run on a remote service. No local store on a phone can replace that.

The difference between a good and a bad solution here is not whether it works, but how it tells you. The bad one fires the request, waits thirty seconds, then gives a generic error — or worse, quietly swallows the text you typed. The good one stops immediately, without a network request, and says that this needs a connection.

What is not network AI, though, has to work offline. The daily question downloaded earlier, locally generated templates, statistics computed from your own data — none of these need a server. If an app disables those offline too, that was a convenience decision, not a technical necessity.

Why is it so rare?

It is worth understanding why this is not standard equipment in 2026, because the answer also shows what to expect in future. There are three reasons, and none of them is technical laziness.

Offline support is more expensive to build. If the data lives on the server there is one truth, and that is that. If it also lives on the device there are two — and for every single feature you have to decide what happens when the two differ. That is not a switch but a design decision you carry from day one. Retrofitting it onto an online system is roughly a rewrite.

Most apps run in a browser. That is not a problem in itself — local storage works in a browser too — but only if the app deliberately prepares for it: stores itself on the device and does not fetch data again for every screen. Without that, losing the network means a blank page immediately.

And a less comfortable reason: offline use does not show up in the statistics. For a service measured in daily opens, offline writing is invisible — it sends no request and generates no data. Anyone who builds it anyway is optimising for the user’s convenience rather than their own metrics.

Where Mirrify stands

In Mirrify offline support is not a feature added later but a founding principle: every write goes to the device first, and the interface works from there. That is true of the journal, the goals, the habits, the finances and the vision board alike — not only of writing.

The upload is a separate, asynchronous process. If there is no network the change stays marked, and it retries on four different events: when the network returns, when you bring the app to the foreground, on a regular timer, and at app start. A bar at the bottom shows how many changes are waiting to upload — we show it deliberately, because trust without verifiability is not worth much.

A network error must not lock you out of your own journal: there is a local copy of your subscription state, and if even that is missing, offline the gate stays open. What does not work: the AI pages. There it stops immediately, without a request, and says why — as discussed above, and the same rule applies to us.

If your current app cannot work offline

You do not have to switch straight away. There are three steps, and the first two are free.

1. Use an intermediate place. The phone’s built-in notes app almost always works offline. Write there, and copy across when you have a network. Inconvenient, but it loses no data.
2. Put the date on the first line. If material accumulates in the intermediate place, the date is the only thing that gives it back its place in time later. More on this in our article on switching.
3. If it comes up regularly, switch. If you run into it several times a month, that is no longer an inconvenience but a standing risk of data loss.

And one thing that is true offline and online alike: your data has to be exportable. If you cannot take what you wrote out at any time in a readable format, local storage alone does not protect you. That is what the seven questions for any journal app are about.

Frequently asked questions

What exactly does it mean that a journal app works offline?

Three different things get called that. At the first level nothing works without network. At the second you can read but not write. Only the third is real: you write, you save, the entry is on the device immediately, and it goes up on its own when the network returns. Instead of the description, the best test is airplane mode.

How do I test it in two minutes?

Put the phone in airplane mode and close the app completely — not just to the background. Then reopen it, try to write, and also check the earlier entries, the goals and the search. Many apps only work without network as long as they have already loaded once.

Can I lose an entry I wrote offline?

In a well-built system, no: the write goes to the device first, the system marks that it has not gone up yet, and that mark survives closing the app. The risk is in apps that only hold the text in memory until saving — there a single close is enough to lose it.

What happens if I also wrote on another device?

This is the most important question. In the weak solution the device that connects last overwrites everything, and the entry written offline disappears. In the good one the system merges the two. Simple trial: write on both devices in airplane mode, then switch the network back on — if both entries are there, it merges.

Why does AI not work offline?

Because it runs on a remote service, and that cannot be replaced on a phone. The difference between a good and a bad solution is not whether it works but whether the app tells you immediately or makes you wait half a minute for a generic error. What is not network AI — the cached daily question, local statistics — has to work offline.

Does Mirrify work without internet?

Yes, and not as a feature added later: every write goes to the device first and the interface works from there, and that is true not only of the journal but of goals, habits, finances and the vision board. The upload runs separately, and a bar shows how many changes are waiting for it. AI features are the exception — those need a network.

Can a network error lock me out of my own journal?

In a good system it must not. There is a local copy of the subscription state, and if even that is missing, access stays open offline. An app that decides about entry from a network response will lock you out of your own data in a moment of bad signal.