Offline-first in practice: what works with no signal

Leanfinit apps store data on the device, so logging, editing and viewing work with no signal. Tomas explains what works offline and what still needs a network.

Tomas·4 min read

An app is offline-first when it reads and writes its data locally and treats the network as optional. Leanfinit apps keep user data on the device with no backend by default, so the core of what people build, logging, editing, searching and viewing their own records, keeps working with no signal. Some things still need a connection, and it's worth knowing which before you build.

Why "offline" keeps coming up

Offline isn't an edge case for the apps we build for. It's where they get used:

a training log in a basement gym with no reception;
a stock or delivery checklist in a warehouse or a van;
a field notes app on a farm, a trail or a building site;
a travel budget used abroad without a data plan;
a study or flashcard app on a commute through tunnels.

Most cloud-first apps handle these moments badly. The screen loads, the spinner turns, the entry you typed disappears or gets saved twice. People learn not to trust the app at the exact moment they need it.

What works with no signal

Because the data layer of a generated app lives on the device, everything that only touches the user's own data works offline:

ActionOffline?
Opening the app after it has been loaded onceYes
Adding, editing and deleting entriesYes
Viewing history, totals and charts built from your entriesYes
Searching and filtering your recordsYes
Timers, counters, checklists and reminders that run on the deviceYes

There is no "sync failed" state for local data, because there is nothing to sync. A set logged in the gym is saved the moment you tap save.

What still needs a connection

Offline-first doesn't mean the network never matters. These need a connection:

The first load of a published web app. The app has to reach the device once.
Building and editing the app in the studio. Generation happens on our side, so changing the app itself requires being online.
Anything that fetches outside data. Exchange rates, weather, maps or a public API need the network by definition.
Sharing between people. Two people editing one list in real time need a shared service, which is a different architecture.

A useful rule: if a feature uses only what the user typed into the app, it works offline. If it needs someone else's data, it needs a network.

How to describe an offline app well

The studio builds from your description, so say what matters about connectivity. Some examples of prompt lines that help:

"This will be used in a gym with no signal. Saving must never depend on the internet."
"Show the last value I entered for each exercise, even offline."
"Add a button to export everything to a CSV file, so I can back it up."
"No login. Open straight to today's list."

The last two matter because offline and no-account go together. If the app doesn't depend on a server, it doesn't need to know who you are.

The part people forget: backups

Data that lives only on a device can be lost with the device. That's the honest cost of offline-first. The fix is cheap: ask for an export or backup feature, and save the file somewhere you control. For anything you'd be upset to lose, such as months of training logs or a parent's medication history, make that part of the first prompt, not an afterthought.

I go through backups, sync and sharing in more detail in No backend by design.

Why we build this way

We could have built every app on a hosted database. It would make some features easier, like syncing across devices, and it would give us a dashboard of everyone's data. We chose not to, for three reasons:

1Reliability. An app that never waits for a server is faster and has fewer ways to fail.
2Privacy. Data we never receive is data we can't expose. Barbara covers this in Private by architecture, not by policy.
3Longevity. A personal tool should keep working for years without a hosting bill or an account that can expire.

Most of what Leanfinit is for is a personal tool for one person. For that, offline-first is simply the better default.

Checking any app for offline support

Before you trust an app with daily logging, test it the simple way: turn on airplane mode, open it, add an entry, close it, open it again. If the entry is still there and nothing complained, the app is offline-first. If you see a spinner or an error, it depends on a server for basic work.

Our guide to a tracking app that works offline, without internet or an account shows what to ask for when you build one yourself.

Describe the app you need for the places with no signal: studio.leanfinit.com.