Kiosk, staff tablet or the customer's own phone
Three ways to put a self-service journey in front of somebody. The screen is the least important difference between them.
The question arrives in the same shape every time: could we not just use a tablet? Sometimes the answer is yes, and it saves an enclosure, a mounting survey and a hardware procurement. Often it is no, and the reason has nothing to do with the size of the display. It has to do with who touches the device, whether anybody is watching, what is bolted to it, and who is excluded when the interface assumes a smartphone user.
AtashiTech builds all three. Packaged kiosk solutions run as locked-down Windows applications, tablet applications cover staff and assisted use, and mobile apps put part of the journey on the visitor's own phone. So the recommendation is not driven by what we happen to sell; the verdict names the cases where a tablet or a phone is the better answer.
Public kiosk, staff tablet and customer phone, criterion by criterion
Eight criteria that settle most of these arguments. Each card gives the practical position for all three.
Who uses it
- Public kiosk: anyone who walks up, once, with no training and no account.
- Staff tablet: a known, trained person who signs in and is accountable for the session.
- Customer phone: a self-selecting group who already own a suitable device and are willing to install or open something.
Supervision
- Public kiosk: unattended by design; every exception has to be handled on screen or by an attendant alert.
- Staff tablet: attended, so the person holding it resolves exceptions themselves.
- Customer phone: unattended and remote, so nothing can depend on a person being nearby.
Durability and environment
- Public kiosk: fixed, powered, mounted, and specified for the dust, grease, glare or weather of its location.
- Staff tablet: survives a shift in a case, needs charging, and walks off if it is not tethered.
- Customer phone: the environment is somebody else's problem, which is an advantage until the network in your building is the problem.
Peripherals
- Public kiosk: printers, scanners, scales, cash devices, biometrics and gate relays wired in and always present.
- Staff tablet: a Bluetooth printer or scanner, a camera and little else without a bag of accessories.
- Customer phone: the camera and nothing else; no printing, no cash, no gate.
Accessibility
- Public kiosk: reach ranges, large type, audio prompts and a language switch are designed once and apply to everyone.
- Staff tablet: the operator's device, so accessibility is about the staff member, not the visitor.
- Customer phone: excludes anyone without a smartphone, data or the confidence to use one, which in a public setting is a real share of visitors.
Lockdown and data exposure
- Public kiosk: the shell is replaced, the session clears on timeout, and nothing of the previous person survives on screen.
- Staff tablet: a managed device signed in to an identified user, so the data boundary is the user, not the session.
- Customer phone: unmanaged; assume the device is compromised and keep the sensitive step on your side.
Estate management
- Public kiosk: a health agent reports uptime, paper and faults to a fleet dashboard; content is pushed centrally.
- Staff tablet: enrolled in an MDM, with charging, loss and replacement as the ongoing overhead.
- Customer phone: nothing to manage, but nothing to control either; you inherit every OS version in circulation.
Best fit
- Public kiosk: unattended journeys with peripherals, money, identity or a gate at the end.
- Staff tablet: assisted journeys, roaming staff, and anywhere a fixed unit cannot be mounted.
- Customer phone: the part of a journey that happens before or after arrival.
Durability is about the setting, not the specification sheet
A device used by the public, all day, by people who did not buy it, is treated very differently from one issued to a named employee.
A fixed kiosk is mounted at a chosen height, powered from the wall, and specified for its location: dust and vibration at a plant gate, grease and heat in a food court, glare and rain on an office porch, and cleaning chemicals in a hospital lobby. Nobody has to remember to charge it, nobody can carry it away, and a watchdog restarts the application after a power cut with no one present.
A tablet used as a public terminal inherits none of that unless somebody supplies it: a floor stand, a locking case, a permanent power feed, a way to stop the device sleeping, and a plan for the shift when the battery is flat anyway. That is achievable, and we build kiosk-mode tablet applications for exactly this pattern. It is simply not free, and the saving on the enclosure is smaller than it first appears once the mount, the case and the charging are added.
The other half of durability is the software. Our Windows versus Android comparison covers the lockdown and update differences that decide whether an unattended device stays on the journey it was set to.
What has to be attached decides more than anything else
List the devices the journey needs. The form factor usually chooses itself from that list.
A badge or receipt printer, a document or passport reader, a barcode scanner, a weighing scale, a cash or coin acceptor, a card terminal, a fingerprint reader and a turnstile relay are all normal parts of a kiosk journey, and a kiosk is the only form factor where all of them can be present, powered and available to every user without anyone fetching them. The categories AtashiTech integrates, and how a new device is qualified, are set out on the integrations page.
A tablet can carry a small subset: a Bluetooth receipt printer, a scanner sled, the built-in camera as a document or QR reader, and an Android-native payment terminal in some formats. That is enough for assisted check-in, a survey, a table-side order or a supervisor's toolbox talk. It is not enough for self-checkout with a scale and a cash recycler, for cash collection, or for a visitor badge printed on the spot.
A phone carries the camera. It scans a QR code, photographs a document and displays a pass, which makes it excellent for pre-registration and for showing a token, and useless for anything that has to be printed, weighed, paid in cash or physically opened.
Who is excluded by each choice
A public-facing journey is judged by the person who has the most difficulty with it, not by the average user.
A kiosk can be designed so that a wheelchair user reaches every control, type is large enough to read without glasses, audio prompts guide someone who cannot read the screen, the regional language is offered first rather than buried, and a help button summons a person without discarding the session in progress. Those are design decisions taken once and applied to every visitor, and they come out of the UI/UX design work rather than being added later.
Moving the journey to the visitor's phone quietly moves the accessibility problem onto the visitor. It assumes a working smartphone, enough data, a charged battery, sufficient eyesight for a small screen, and the confidence to use an unfamiliar interface at a counter with people waiting behind. In a hospital OPD, a government service hall or a factory gate, that assumption excludes a substantial group of exactly the people the service exists for. A phone journey should therefore be an additional route, never the only one.
A staff tablet sidesteps the question by putting a trained person between the visitor and the software, which is a legitimate answer where the volume is low and the staff exist. It is not self-service; it is a faster counter.
The phone is usually the other half of the kiosk, not its replacement
The strongest deployments use both, each for the part it is good at.
A visitor pre-registers on a phone and receives a QR code, then scans it at the lobby kiosk, where the badge prints and the turnstile opens. A patient books an appointment on a phone and checks in at the registration kiosk. A customer takes a queue token remotely and watches the position on the phone while the kiosk and the display boards run the queue in the building. A technician receives a fault alert on a phone from the fleet management platform and clears it on site.
In each of those, the phone removes typing and waiting, and the kiosk does the part that needs hardware, identity or a physical outcome. Splitting the journey that way is more useful than arguing about which device should own all of it.
Which one to choose
A neutral reading of the criteria above.
Choose a public kiosk when the journey is unattended, when anything must be printed, scanned, weighed, paid in cash or physically unlocked, when the users are the general public rather than staff, or when accessibility and language inclusion are part of the obligation. Registration, induction, collection, checkout and check-in almost always sit here.
Choose a staff tablet when a trained person is holding the device: assisted check-in at a busy reception, a supervisor running a toolbox talk, table-side ordering, ward-round data capture, or a store associate looking up stock. It is also the right answer where no fixed unit can be mounted or powered.
Choose the customer's phone for the parts of the journey that happen before arrival and after it, and treat it as an addition to a kiosk rather than a substitute for one. Making it the only route excludes people.
Decide after the journey is written down, not before. Our scoping and quoting process produces the step list and the device list that make this choice obvious, and buying versus building is the decision that follows it.
Tablet, kiosk or phone for your journey?
Describe the journey, who performs it and what has to be printed, read or opened at the end of it. We will say which form factor fits, including when a tablet is the cheaper right answer.
Frequently asked questions
Tell us the journey, the sites and the hardware you already have — every engagement is scoped and quoted individually.