What can I do in the app?

Signing in without typing

The web interface generates a QR code with a short-lived token. The app reads it, and you are signed in without anyone typing a password on a phone keyboard.

After that the app keeps its session through a refresh token that is managed on the server and invalidated on sign-out. Anyone belonging to several businesses picks one after signing in and switches later without signing in again.

Recording time

The stopwatch is fully there: start, pause, resume, stop, cancel. It runs on the server, so you can start it on the computer and check it on the phone.

There is also manual entry, and two things that save repetition: copying from the previous day and from the previous week, plus the suggestion list from shifts that were planned but not recorded.

• Time entries can be created, changed and deleted in the app.
• Where the permitted recording channel does not allow editing, the change request is the intended route, and that works in the app too.
• The app flags breaches of occupational safety and recording rules separately; they come from the same check as in the browser.

Requesting and deciding

Employees make their absence requests in the app and change and cancel them. There is also a separate view of the team's absences, as far as they should be visible.

Anyone who decides finds the open absence and payout requests in the app as well and decides them there.

Shifts and the day plan

The whole handling of your own plan also works on the phone: the shift list and shift detail, confirming and declining, swaps, applying for open shifts, the shift market and the pickup request when somebody drops out.

For businesses working with the day plan the same applies at the level of individual blocks: the day view, applying for a free block including the decision, handing a block over, picking one up when somebody drops out and the lighter first step of registering interest in a block.

• The shift features check the plan in the channel itself, independently of the web interface.
• Without the shift planning module these views are not present.

Your own account

The start view carries the figures that matter day to day: recorded today, the weekly position, the balance and remaining holiday. They come from a dedicated route rather than from many individual calls.

The time account can be called up for a particular year. Without a year the service decides which year is the current one, because that depends on the business's time zone.

Settings and master data

The profile, profile picture, appearance, notification preferences, the calendar token and your own working-time model are reachable in the app.

So that time tracking works without reloading, the app keeps a store of master data: clients, services, the assignment of services to clients, projects, allowances and the most recently used bookings.

What the app does without a network, and what it does not

The app sends collected operations in one call for processing and, in return, fetches only the changes since its last state. That keeps it fast and economical.

That is not offline operation with conflict resolution, though. There is no merging of two divergent states. An operation that fails the business rules fails and has to be repeated.

The third route: the fixed terminal

Alongside the phone and tablet there is the wall-mounted terminal in the business, a device with an RFID reader and its own application. Staff clock in and out with a transponder, without signing in on the device.

It is attendance recording and not access control: it opens no doors and replaces no locking system. How it is set up is described in the terminal guide.

How the interface is built

All the app's addresses sit under one version. A request without a version is rejected with a clear message and the list of available versions, rather than running into nothing.

Every route runs through the same validation layer and returns the same response shape, with a success and error envelope including validation errors. Even the business-wide setting of whether recording happens via web, app or both takes effect at the app boundary and not only in the interface.