Design shared-device apps for the next person who picks up the phone

Make identity, handover and unfinished work explicit on phones and tablets used by a team.

Two team members handing over a shared tablet at a packing bench.

A shared warehouse phone or reception tablet is a different product environment from a customer's personal device. Several people may use it during one shift, and the next person may not know who last signed in or what remains unfinished. The app should make current identity and task ownership visible enough to prevent mistakes without exposing unnecessary information at the handover.

Separate device ownership from identity

At an event-hire depot, a shared phone may belong to the business while individual staff members record returns. Show who is currently acting and provide a practical switching flow. Do not assume the person holding the device is the same person who opened the app that morning. If actions need an accountable record, shared credentials undermine that meaning. Android's Credential Manager documents supported sign-in experiences, but the business must still define how staff identify themselves and how access ends when someone leaves the shift or the organisation.

Make handover a real workflow

Before a user switches, identify any unsent work and explain what will happen to it. A photo waiting to upload should not become the next person's unexplained attachment. Decide whether drafts belong to the individual, the device or an assigned job, and show that distinction. On a customer-facing tablet, offer a controlled presentation view that excludes staff-only notes. After the customer finishes, return to a neutral state rather than leaving their details visible to the next visitor. Test the complete handover with people who have not watched the previous session.

Prepare for unavailable devices

Staff should know how to report a missing shared phone and how to continue essential work through an approved alternative. Avoid storing more customer information on the device than the workflow needs. Discuss device management and access controls with the responsible technical team, then express the resulting behaviour clearly in the app. Rehearse an interrupted shift change, a forgotten sign-out and a device that comes back online later with queued work. The records received by the office should still identify the correct person and task, without requiring guesswork about who held the phone.

  • Can the next user immediately tell whose account and work are active?
  • Who owns a draft that remains on the shared device at shift change?
  • Does customer presentation mode hide internal notes and previous customer details?
  • What happens to queued work when a user changes or access is withdrawn?

Further reading

Discuss your software project with 110s

Related Insight