The gym is an unreliable network environment

Basements, crowded buildings, captive Wi‑Fi, and brief handoffs between networks make connectivity inconsistent. A live workout should not wait for a remote request before confirming a set.

Offline-first design makes the local write the ordinary path. A network becomes an optional route for backup or synchronization, not a prerequisite for recording the session.

Offline first is more than cached screens

A cached exercise list is useful, but it does not protect an active session. A complete offline path includes starting a workout, adding exercises and sets, editing values, leaving and resuming, finishing, and reviewing local history.

Meaningful edits should persist immediately. If the app closes, the next launch should recover the unfinished session from durable storage rather than hope an in-memory state survived.

Local authority changes the account relationship

When core data belongs in a device database first, an account can remain optional. People can evaluate and use the product without handing over an email address simply to record a squat.

Cloud access can still be valuable for backup and browser use. The important distinction is consent: the user signs in and chooses to upload, and the product explains that a browser can see only synchronized data—not the phone’s private SQLite file.

Synchronization still needs conflict behavior

Offline systems eventually meet concurrent edits. A website and phone may both start from the same backup and then diverge. Silently accepting the last request can erase the newer version.

A conservative first approach is version checking: reject a stale write, show the conflict, and ask the user to reload or explicitly choose a direction. More granular merging is possible, but it requires entity-level versioning and well-defined rules for every record type.

Export remains important

Cloud backup is not a substitute for portability. A lossless export provides an independent copy, while a simple CSV helps people inspect completed training outside the product.

Offline-first architecture cannot guarantee against device loss, storage failure, or user deletion. It can make ordinary training dependable and give users clearer choices about where their history lives.