Offline meal planners and apps with no account

The supermarket problem

Large shops are built out of steel, concrete and freezer cabinets, which is more or less the recipe for a Faraday cage. Mobile signal inside them ranges from poor to absent, and that is precisely where you need your shopping list.

An app that fetches your list from a server when you open it will show you a spinner. An app that keeps the list on your phone will show you the list. That single difference is the strongest practical argument for on-device meal planning, and it has nothing to do with privacy.

Offline means two different things

App listings use the word loosely, and the distinction changes what you are actually buying.

• Offline-capable: the app normally talks to a server but caches enough to survive a dead zone. It still wants an account, and it syncs again when you reconnect.
• On-device only: there is no server anywhere in the design. Your data was never elsewhere, so there is nothing to fall back to and nothing to reconnect.

What on-device costs you

An honest account has to start here, because what you give up is not nothing.

• No syncing — your plan lives on one phone, and a second device starts empty
• No shared household plan — your partner cannot see or edit the same week
• No automatic backup — lose the phone without an export and the data is gone with it
• No importing a recipe from a web address, which needs a server to fetch and parse the page

The backup point deserves emphasis

With no server, the only copy of your recipes is the one on your device. There is no support team who can restore it, because there is nothing on their side to restore it from.

Any app built this way should give you a one-tap export to a file you can actually read and store somewhere else — and you should use it, on the day you finish typing in your recipes rather than the day after you drop your phone in a canal.

What you get in return

The compensations are real, and several of them are guarantees rather than promises.

• It works in the shop, in the basement, on a plane, and in a rented cottage with no signal
• There is no account to create, no password to keep, and no email address to hand over
• Your recipes and photos cannot be leaked from a server that does not exist
• No analytics and no tracking, because there is nowhere for it to be sent
• The app cannot be switched off remotely when a company loses interest in it

Why most apps want an account anyway

Accounts are not usually a land grab. They are the price of the features people ask for most loudly.

Syncing a phone and a tablet needs somewhere for the two to meet. A shared family plan needs identity, because the app has to know which devices belong to one household. Cloud backup needs a cloud. Every one of those is genuinely useful, and none can be built without a server and some way to identify you.

So the question is not whether accounts are bad. It is whether you are getting one of those features in exchange for yours.

How to test an app before you rely on it

Five minutes of checking, done before you enter fifty recipes, is worth more than any listing description.

• Turn on airplane mode and open the app — can you still see your list?
• Find the export function before you commit, not after
• Search the privacy policy for the word "analytics"
• Check whether the features you care about are the ones requiring the account
• Ask what happens to the app if the company stops paying its server bill

Where Cooklendar sits

Cooklendar is on-device only: no accounts, no servers, and nothing transmitted anywhere. Your recipes, plans, lists, pantry, photos and nutrition log stay in the app’s private storage on your phone, which is why it works in the shop and why there is no analytics in it.

It also means every limit above applies. There is no sync and no shared plan in this release, and the export in Settings is your only backup. That is the trade, stated plainly, so that you can decide whether it is the right one for your kitchen.

Common questions