The Mobaro mobile app is built for mixed-connectivity operating environments — from tablets in indoor control rooms with reliable wifi to phones at outlying water park stations with intermittent cell signal. This article explains exactly how the app behaves in each state, how to prepare for offline use, what happens to your work when connectivity drops, and how to confirm everything synced when you're back online.

Two prerequisites before you can rely on the app offline:

The first sign-in seeds the device with your User context, assigned Schedules, Locations, and basic configuration. Without that initial sync, the app has nothing to work with offline.

By default, Checklists are not downloaded to the device. To make a Checklist runnable offline:

The Checklist's full content (questions, logic, attached Library references) downloads to the device. Repeat for every Checklist you'll need offline.

The Mobaro mobile app shows three connection states via the indicator in the lower-right of the home screen.

Strong enough internet connection to talk to the Mobaro server. Everything you do is syncing in real-time. Photo uploads are immediate. The Pending uploads counter shows zero.

No usable connection to the Mobaro server. This includes truly offline (no signal at all) and weak/intermittent connections that can't reach the server. You can keep working — Checklists you've downloaded for offline can be completed, Assignments can be created and resolved, photos can be captured. Everything queues locally on the device.

Connection has just been re-established and queued items are uploading. The number indicates remaining items to upload — it ticks down as uploads complete.

Works offline:

Does not work offline:

When you're offline (or have a weak connection that can't reach the server), every action that would normally sync is queued locally and counted on the Pending uploads tile on the home screen.

The counter increments as you work and decrements as items upload. Watch for:

If, after finishing a Checklist on the mobile app, the Result doesn't appear on the web Backend or your email Notification doesn't arrive, the Result is likely still queued locally.

Open a browser on the device and navigate to app.mobaro.com. If the page doesn't load, your device's internet is the problem — fix that first.

If the counter is decreasing, the app is uploading queued items — wait for it to reach zero. If the counter is stuck non-zero, the app can't reach the server even though browsers can.

On iOS, swipe up the app from the recent apps view. On Android, swipe it away. Re-launch. The app re-attempts the queued uploads on launch.

Once the counter shows zero, the Result is on the server. Check the web Backend to verify it appears.

If the queue won't drain after the steps above, capture a screenshot of the Pending uploads tile and email [email protected] with your User and the approximate time the work was completed.

Scenario: An operator's tablet shows a strong wifi connection but the Mobaro app's Pending uploads counter has been stuck on 7 for the past hour.

Setup: Operator opens a browser, visits app.mobaro.com — the page doesn't load. The wifi has internal connectivity but no internet.

Result: The "wifi connected" indicator was misleading. Once moved to a working network (or after IT fixes the wifi gateway), Pending uploads decrements to zero.

Scenario: A water park lifeguard knows their station has poor cell signal. They want to be ready for offline operation.

Setup: Before heading to their station, on the lobby's wifi, they open Mobaro, swipe left on each Checklist they'll run today (pre-opening, hourly water test, end-of-shift), and tap Download for offline. The downloads complete in seconds.

Result: All day at the station, even with no cell signal, they complete Checklists normally. The connection indicator shows red, Pending uploads accumulates. At end of shift back in the lobby, everything syncs in 30 seconds.

Scenario: A supervisor expected an email Notification at 11am from a completed safety Checklist Result, but it never arrived.

Setup: Supervisor pings the operator. Operator checks their Mobaro app — Pending uploads shows 3. Operator confirms wifi has actual internet. Force-closes and reopens the app.

Result: Pending uploads decrements to zero. The Result lands on the Backend. The Notification email arrives a moment later. Supervisor logs the late delivery for the team's process review.

Q: How long can I work offline?
A: Indefinitely, as long as the device has battery and storage. The queue holds however many items it needs to. Practical limit: very long offline windows can build large local queues that take longer to sync — try to come online at least once a day.

Q: Will photos be captured at full quality offline?
A: Yes. Offline photos are stored at the same quality as online — they just upload later. If you have lots of photos pending, expect the upload to take longer when you reconnect.

Q: What happens if my device runs out of storage while offline?
A: The app warns you. New photos and Results may fail to capture if storage is full. Free up device storage if you see a warning, or come online to drain the queue.

Q: Does Pending uploads survive an app force-close?
A: Yes. Queued items persist across app sessions. Don't sign out or uninstall while items are pending — that's the risky operation, not closing the app.

Q: My device clock is wrong. Does that affect offline timestamps?
A: Offline timestamps come from the device clock at the time of capture. A device with a wrong clock produces wrong timestamps. Make sure devices used in the field have automatic time-sync turned on.