Desktop-only time tracking works fine for roles that spend the whole day at one machine, and misses a substantial share of the work in roles that don't — field service visits, in-person client meetings, warehouse or facility work, anything that happens away from a keyboard. Clockframe's mobile app exists specifically to extend accurate time tracking to that kind of work, rather than leaving it to be reconstructed from memory at the end of the day.
What the mobile app actually covers
The mobile app supports manual clock-in and clock-out tied to a specific project or task, the same category and tagging structure used on desktop, and optional, clearly-disclosed location tagging for field-service use cases specifically — tagging a time entry with a job-site location, not continuous background location tracking of a person's whereabouts throughout the day.
The app is intentionally simpler than the desktop product, rather than a full feature-parity port squeezed onto a smaller screen. Reporting and analytics, discussed on the product side of this site, are available for viewing on mobile but are primarily built for the desktop or web dashboard, since detailed report review is rarely something someone wants to do from a phone in the field. The mobile experience is optimized instead for the handful of actions someone actually needs to perform quickly, standing at a job site or between appointments: clock in, clock out, switch tasks, check a schedule. A supporting example appears this supporting resource.
Where the line is drawn deliberately
- Location tagging, where enabled, applies to specific clock-in/clock-out events at a job site — not continuous, always-on GPS tracking of an employee's movement.
- The mobile app does not capture screen activity or app usage — that category of monitoring, covered elsewhere on this site, is desktop-specific by design, since it doesn't have an equivalent meaning on a personal phone.
- Offline clock-in/out is supported and syncs once a connection is available, for field locations without reliable signal.
- An employee's own time entries, on mobile exactly as on desktop, remain visible to that employee under the same symmetric-access principle discussed in the reporting guide on this site.
- The app requests only the specific device permissions needed for its actual features — location access is requested and explained at the moment it's relevant to a specific action, not bundled into a broad, unexplained permissions request at install time.
- An employee can review and, where the organization's policy allows, delete their own location-tag history from within the app, rather than that data being visible and manageable only from an administrator's side.
Why this matters more on a personal device than a company one
Because a mobile app frequently runs on a personal device — many organizations don't issue dedicated work phones to field staff — the scope discipline described above carries more weight here than the equivalent discussion for a company-owned desktop. A desktop machine provided by an employer for work is more clearly, unambiguously a work context; a personal phone that happens to have a work app installed is not, and treating the two identically for monitoring purposes would ignore a real and important distinction most employees, and most monitoring-law frameworks discussed elsewhere on this site, draw between the two.
How this shapes what the roadmap does and doesn't include
Feature requests for the mobile app periodically include more granular location tracking, on the reasoning that it would provide better visibility into field staff's actual movement and route efficiency. Clockframe has consistently declined to build this as a general feature, for the same reason discussed in the what-monitoring-should-never-do guide elsewhere on this site: continuous location tracking of a personal device crosses from job-related tracking into something closer to personal surveillance, and the specific, job-site-tagging approach already addresses the legitimate underlying business need — knowing a job was completed at the right location — without the broader privacy cost. For further background, consult Okta resources.
This distinction matters specifically because a mobile app, more than a desktop client, sits on a device that also holds someone's entire personal life — which is exactly why the product's mobile scope is narrower and more specifically job-related than its desktop scope, not the same feature set ported over by default.