Read this before a flight. The short version: on the web, food and water you
log with no connection are kept and sent once you are back online. The ClapDiet
mobile app needs a connection, and logging in it without one does not work.
On the web
Food and water you log in the web app while offline are saved and sync onceyou reconnect. Until each entry has been sent it shows as waiting to sync, and
you do not need to type it twice.
Some features need a connection, such as AI meal recognition from a photo or a
description, and relogging an entry from your history. Nothing else you save is
queued either: a weight entry saved with no connection is not saved, so enter it
again once you are back online.
Open the page you log from before you lose the connection. A page that has not
loaded yet cannot be opened offline.
Entries that have not synced belong to the account that logged them. Signing out
deletes them from this browser, and ClapDiet tells you how many there are first,
so you can stay signed in and let them sync. If a different account signs in here,
the previous account's entries that have not synced are deleted, never sent to the
new account.
In the mobile app, do not log without a connection
In the mobile app, a meal, a glass of water or a weight saved with no signalis not saved. It is not queued, it is not held on the phone, and it does not
upload later. The save fails and the entry is gone.
The mobile app has no offline write queue. We would rather tell you that than
have you log a day of meals on a plane and land to find them missing.
If you will only have your phone while offline, note what you ate somewhere
else — your phone's notes app is fine — and enter it when you are back.
What the mobile app can still show
Three screens keep a copy of what they last showed you, for 24 hours:
Open one of them with no connection and it shows you that copy rather than an
error. Everything else on the screen behaves normally, which means anything
needing fresh data will not load.
The rest of the app — the food database, your labs, your plan, insights,
settings — needs a connection every time.
The mobile app does not know it is offline
There is no offline banner, no cloud-with-a-line icon and no offline mode to
switch into. The mobile app cannot currently detect that your connection has
dropped: it tries, waits, and shows you an error or an empty screen.
That is why the advice above is about what you do rather than what the app
does. A screen that fails to load with no explanation is almost always this.
When you are back online
On the web, your waiting food and water entries are sent without you doing
anything. In the mobile app nothing happens automatically, because nothing was
waiting. Pull down to refresh the screen you are on, or leave and come back to
it, and it loads normally again.
Preparing for time offline
There is nothing to download by hand, and no setting to turn on. What genuinely
helps:
still have a connection, if you want to be able to look at them later
largest transfers
In a poor signal area
Slow is different from absent. On a weak connection screens will load, just
slowly, and saving works — it may simply take a few seconds. The mobile app
retries a failed request twice before giving up, so a brief dropout often
resolves itself without you noticing.
What we would like this to be
An offline log queue is the missing piece in the mobile app, and we know it.
Until it exists there, the honest guidance for the app is the guidance above.
Related Articles: