A shared floor tablet is not a phone with more users. It is a public terminal in a hostile environment, and designing for it means giving up several conveniences that single-user mobile apps take for granted.
The constraints a shared device imposes
- No persistent login. Whoever picks the device up next must not inherit the previous user's session or see their draft.
- Identity has to be lightweight. A password on a greasy screen with gloves on will be shared, written on the wall, or bypassed - a scanned badge or a short PIN is more honest.
- Sessions must expire fast and reset cleanly, because devices are put down mid-task constantly.
- The screen is read at arm's length in poor light. Type sizes and contrast that pass in the office fail on the floor.
- Connectivity is worse near the machines than anywhere else in the building, so every step must queue offline.
Designing the triage flow
Badge or QR identification attaches the reporter without a keyboard, which is what makes attribution survive contact with the floor.
Shared devices get put down. A flow with one question per screen resumes cleanly; a long form does not.
Name and picture the actual isolation point for that asset. Generic safety text is ignored because it is always the same.
Do not restart, do not open the rear guard, do not clear the jam by hand - written per machine, because the answer differs per machine.
Submit, confirm, and return to the idle screen without leaving anything behind for the next user.
Test with gloves on, in the darkest corner of the plant, on the oldest device you own. Every shared-device design failure we have seen was invisible in the office and obvious within ten minutes on the floor.
Designing for shift rotation
Operators rotate across shifts and lines, and turnover is high. Any flow that assumes accumulated familiarity with the software will degrade every time the roster changes.
The practical consequence is that the flow must be self-explanatory on first use, in the reader's own language, with photographs doing the work that instructions cannot. If a new operator on their first night shift cannot complete it unaided, it is not finished.
Measure your real downtime cost.
Firmicore tracks reported and hidden maintenance drag from day one.
Start FreeTharindu (Founder, Lumora Ventures) works with manufacturing teams in Sri Lanka and Southeast Asia to design practical maintenance software for real factory constraints.