Overview
Prepare the Mobaro mobile app while connected before entering an area without coverage. Offline work uses the data already on the device, and completed work waits there until it can upload.
At a glance |
|
Who can do this | Each User prepares their own signed-in Mobaro mobile app. |
Where | Mobile app › home screen, Checklists and Library |
Works on | Backend (web), Mobile app |
Availability | All organizations |
💡 Why this matters: A short preparation check reduces the chance of reaching the work area without the form or instructions you need.
Before you start
This workflow is for the Mobaro mobile app. RideOps needs a connection and is not an offline replacement. Sign in online first; a device with no downloaded account data cannot begin its first session offline.
Walkthrough
1. Confirm the User and organization
Open Profile and check that the correct person and organization are signed in. Use that account throughout the visit. Resolve any login or organization change before leaving coverage.
2. Refresh the working data
On the home screen, use the refresh control while connected. Wait for the refresh to finish, then check the intended Checklist and Location in the work list. Calendar work is downloaded within the supported upcoming window; refresh closer to the work if it is not yet included.
3. Download the required references
Open the manuals and other required Library files while online and use the available download controls. Confirm the actual file opens, not just its title. External web links and streamed content still depend on their own connection requirements.
4. Check the queue after returning
Reconnect as the same User and wait for the upload count to clear. In the home layout shown, the connection tile then displays Connection available. Confirm important Results in the Backend before handing over or resetting the device.
Check the outcome
Offline completion is not proof that a Result has reached the Backend. Keep the app and its data intact until uploads are confirmed. Do not log out, uninstall or clear device data as a way to fix a queued upload. Follow unsent-data recovery if work remains stuck.
Best practices
Prepare on the actual device and account that will do the work.
Keep the device powered during the visit and upload.
Check a representative reference file before leaving coverage.
Frequently asked questions
Can RideOps work offline too?
No. This preparation applies to the Mobaro mobile app. RideOps requires a connection.
Why is offline work missing from the Backend?
It may still be queued on the original device or only saved as unfinished progress. Reconnect with the same account and check uploads before changing the device.
Will new assignments arrive while I am offline?
No. The app works from its downloaded data. Refresh while online to receive new work and changed access before the visit.