Give the mobile task its own design.

A shared inspection phone passes from one staff member to the next. The first person's work is saved locally but has not reached the office. A useful application should make that position understandable without letting the next user mistake pending work for an accepted inspection.

Define the handover on the device

For a hypothetical team in Israel, choose one work reference such as IN-24/A and the actual inspection fields. The client identifies which Hebrew, Arabic or English labels staff require and who can review them. Latin references and required units must stay recognisable beside right-to-left text.

The phone should distinguish a local draft, waiting upload, accepted record and rejected item needing correction. If a person signs out while work remains pending, agree whether it is retained securely for that person, transferred through an authorised process or requires action before handover. Do not let the next person's login become an accidental continuation of the previous session.

Choose the right application

A browser tool may cover a connected occasional task. An installed application needs an agreed reason, such as device capabilities or substantial local work. Camera, scanning and offline behaviour are assessed against actual devices, permissions and the selected implementation.

Try the interruption before rollout

Acceptance includes an interrupted upload, corrected work reference, refused permission and second user opening the device. Confirm the receiving record as well as the screen message. A successful build does not establish physical-device suitability or store approval.

Public distribution and client-owned accounts are scoped where relevant. Bring the shared-device sequence and explain what staff need to know before handing it over. Plan the inspection task →