Offline is not a nice-to-have in pet sitting

Here is a story many sitters will recognize. They are standing in a client’s basement laundry room with the cat, they have taken three photos, they tap check out, and the spinner never stops.

Then the app loses the photos.

The places the work happens

In-home pet care happens in buildings that block signal: basements, interior stairwells, concrete mid-rises, garden apartments with the utility room in the back. It happens on rural roads with one bar. It happens in elevators.

Treating connectivity as a given is not a small oversight in this category. It is a mismatch with the job.

What offline-first actually means

Not "we cache the schedule". Offline-first means every mutation is written to local storage first and the network is a background detail. Check in, checklist, photos, video, notes, the message to the client, even the audit entry for revealing the lockbox code, all queued locally, all replayed in order later.

It means photos are compressed on the device so a full day of offline work does not exhaust storage. It means the queue survives a force-quit. It means replaying the queue twice is safe, because every item carries an id and the server treats it as an idempotency key.

And it means recording both clocks. A visit completed at 7:02am in a dead zone and synced at 4pm should read as 7:02am on the client’s report card, and should still be auditable as having arrived at 4pm.

The test we hold ourselves to

Put the device in airplane mode. Complete a full visit: check in, checklist, three photos, a note, check out. Turn the radio back on. Every artifact appears correctly, in the right order, with the right timestamps.

That is an automated test in our suite, not an aspiration.