Mobile
Mobile
This domain tests the iOS and Android apps: what they do well, where they differ from desktop, and how offline behaviour and device security change the answer.
What the apps are for
- Daily execution: My Work, notifications, quick task creation, updating status and assignees, attaching photos from the camera, starting and stopping time tracking, and reading Docs and chat.
- Widgets and push notifications make the app a triage tool. Notification preferences are per device and separate from email and desktop settings.
- Offline support is limited: recently viewed and cached content is available, and some changes queue until connectivity returns. Conflicts are possible if someone else edited the same fields.
- Administration is desktop-first. Permissions, ClickApps, integrations, billing, and workspace structure are not managed from the phone.
- Security leans on the device: passcode and biometrics, MDM-managed deployment in regulated organisations, and remote session sign-out if a device is lost.
Worked example
A field crew must update task status and attach site photos with poor signal. Pre-load the relevant List while on Wi-Fi, work in the app offline, capture photos, and sync on return. Avoid editing Custom Fields that head office also changes, because queued edits can conflict. The reasoning: the mobile app handles capture and status well, tolerates brief disconnection for new content, and is the wrong place for concurrent structural edits.
Traps that cost marks
- Assuming feature parity with desktop, then hunting for admin settings that do not exist on mobile.
- Believing uninstalling the app deletes workspace data. It does not.
- Assuming offline edits always merge cleanly; concurrent edits to the same field can be lost.
- Changing a mobile notification setting and expecting desktop or email alerts to change.
- Forgetting that a lost device needs a session sign-out, not just an app uninstall.