Gyms are among the worst places on earth for a phone signal. They sit in basements and concrete-heavy buildings, the free weights area is usually the deepest corner, and the Wi-Fi, when it exists, is saturated by everyone streaming something on the cardio deck. This is not an edge case for a workout tracker. It is the primary operating environment.

Which makes it strange how many fitness apps are built like the network is always there. You finish a set, tap to log it, and get a spinner. Or the set saves, but the rest timer stutters because the app is retrying a request. Or the worst version: you log an entire session, the app never actually persisted it locally, and when it finally reconnects the workout is gone. If any of that has happened to you, the app was built online-first, and the gym punished it for that choice.

What offline-first actually means

Offline-first is not "the app has a retry button". It is an ordering decision about where your data lives first:

Every write lands on the device before anything else happens. Logging a set writes to local storage immediately. The network is not in the critical path of the tap. If the request can't go out right now, nothing about your workout changes.
The device copy is what you see. The screen renders from local state, so the app is exactly as fast at rep 1 of a dead-zone workout as it is on your couch on Wi-Fi.
Sync is a background concern. A queue drains to the server whenever a connection exists: between sets, on the walk out of the basement, or an hour later. Order is preserved, and nothing is lost if the app is killed with items still queued.
Recovery is assumed, not exceptional. Phones die, apps get killed by the OS mid-session, browsers reload. An offline-first tracker restores the in-progress session from the local copy on the next launch and continues, because the local copy was always the source of truth for the live workout.

The test is simple: put your phone in airplane mode, do a full session, force-quit the app, reopen it, and then reconnect. If the workout is complete and intact on the server afterwards, the app is offline-first. If anything is missing, it is not.

Why this is harder than it sounds

The reason many apps punt on this is that offline-first is genuinely more work. Two copies of the truth (device and server) must be reconciled, and every feature has to answer awkward questions. What happens if you complete a workout on your phone in the basement while the plan was edited on the web upstairs? Which side wins for set progress, and which side wins for plan structure?

Zirv's answer, for the curious: the server owns the plan's structure, and the device owns the live session's progress. When a session restores, the plan structure comes from the backend and your completed sets, weights, and reps merge back in from the local copy. Structure changes flow one way, training data flows the other, and neither can clobber the other. The same discipline applies on the watch: an Apple Watch session keeps running with the phone in the locker, and the results land when the devices see each other again.

The parts nobody notices, which is the point

Done right, offline-first is invisible. The set logs instantly whether you have five bars or none. The rest timer never hiccups. The session you started before your train went into the tunnel is still running when you come out. A cold-started app resumes the workout you were mid-way through. None of this announces itself; things just never break in the specific ways gym reception tries to break them.

That invisibility is why it rarely makes feature-list marketing, and why it is worth asking about explicitly when choosing a tracker. A feature grid will tell you an app has plans, charts, and a watch companion. It will not tell you whether any of it works forty minutes into a basement session with zero connectivity, and that is the session that decides whether you trust the app with your training.

What to take from this

If you train in a commercial gym, assume bad reception is your default condition and pick tools accordingly. Test the airplane-mode scenario above on whatever you use today. And if you build software of any kind for gyms: the network is a guest in the workout, not a participant. Design like it left, because it will.